# Apache Log4j does not verify the TLS hostname in its Socket Appender Advisory record · `GHSA-vc5p-v9hr-52mj` - **Identifiers:** `GHSA-vc5p-v9hr-52mj` · `CVE-2025-68161` - **State:** Confirmed - **Severity:** CVSS 6.3 Medium - **Critical:** No - **Weakness (CWE):** [CWE-297](https://cwe.mitre.org/data/definitions/297.html) - **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md) - **Published:** 18 Dec 2025 - **Updated:** 10 Sept 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 18 Dec 2025, 21:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.logging.log4j:log4j-core` (Maven): affected `>=2.0-beta9, <2.25.3`; fixed in `2.25.3` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > The Socket Appender in Apache Log4j Core versions 2.0-beta9 through 2.25.2 does not verify the TLS hostname of the peer certificate, even when verifyHostName or log4j2.sslVerifyHostName is set to true. An attacker who can intercept or redirect traffic between the client and the log receiver, and who holds a certificate from a authority trusted by the appender's trust store, can intercept or redirect log traffic. Upgrade to log4j-core 2.25.3, which fixes the issue; alternatively, configure the Socket Appender to use a private or restricted trust root. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:L/SA:N`, from CNA (apache) - **CISA KEV:** Not listed. - **EPSS:** 0.0077, the 56th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:17 UTC: First seen by agentprime - 31 Oct 2026, 14:17 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-vc5p-v9hr-52mj) ## Sources - [GitHub Advisory Database: GHSA-vc5p-v9hr-52mj](https://github.com/advisories/GHSA-vc5p-v9hr-52mj) - [OSV: GHSA-vc5p-v9hr-52mj](https://osv.dev/vulnerability/GHSA-vc5p-v9hr-52mj) - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .