# Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters

Advisory record · `GHSA-h383-gmxw-35v2`

- **Identifiers:** `GHSA-h383-gmxw-35v2` · `CVE-2026-34479`
- **State:** Confirmed
- **Severity:** CVSS 6.9 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-116](https://cwe.mitre.org/data/definitions/116.html)
- **Tags:** [CWE-116](https://agentprime.io/advisories/tag/cwe-116.md)
- **Published:** 10 Apr 2026
- **Updated:** 26 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Apr 2026, 18: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.7, <2.25.4 || >=3.0.0-beta1, <=3.0.0-beta2`; fixed in `2.25.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Log4j Core (org.apache.logging.log4j:log4j-core) versions 2.7 up to but not including 2.25.4, and 3.0.0-beta1 through 3.0.0-beta2, are affected. The Log4j1XmlLayout in the Log4j 1-to-Log4j 2 bridge does not escape XML 1.0 forbidden characters, so it produces malformed XML that conforming parsers reject, which can cause downstream systems to drop or fail to index log records. The source gives few details on attacker requirements. Upgrade to version 2.25.4.

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.9 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N`, from CNA (apache)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0054, the 45th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:16 UTC: First seen by agentprime
- 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-h383-gmxw-35v2)

## Sources

- [GitHub Advisory Database: GHSA-h383-gmxw-35v2](https://github.com/advisories/GHSA-h383-gmxw-35v2)
- [OSV: GHSA-h383-gmxw-35v2](https://osv.dev/vulnerability/GHSA-h383-gmxw-35v2)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-34479>
- <https://github.com/apache/logging-log4j2/pull/4078>
- <https://github.com/apache/logging-log4j2>
- <https://lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on>
- <https://logging.apache.org/cyclonedx/vdr.xml>
- <https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html>
- <https://logging.apache.org/security.html#CVE-2026-34479>
- <http://www.openwall.com/lists/oss-security/2026/04/10/8>

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 (<https://api.agentprime.io/mcp>), 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: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-h383-gmxw-35v2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-h383-gmxw-35v2/>. Everything for agents: <https://agentprime.io/llms.txt>.