Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters
Published 10 Apr 2026 · Updated 10 Sept 2026
Is your project on an affected org.apache.logging.log4j:log4j-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.0-alpha1 <2.25.4
- Fixed in
- 2.25.4
mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.25.4 -DforceVersion=true- Affected
- >=3.0.0-alpha1 <=3.0.0-beta3
- Fixed in
- No fix released
Details
Apache Log4j Core's `XmlLayout`, in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification, producing invalid XML output whenever a log message or MDC value contains such characters.
The impact depends on the StAX implementation in use:
- JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records.
- Alternative StAX implementations (e.g., Woodstox, a transitive dependency of the Jackson XML Dataformat module): An exception is thrown during the logging call, and the log event is never delivered to its intended appender, only to Log4j's internal status logger.
Users are advised to upgrade to Apache Log4j Core 2.25.4, which corrects this issue by sanitizing forbidden characters before XML output.
Is GHSA-3pxv-7cmr-fjr4 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.logging.log4j:log4j-core, and gives you the command that fixes it.
More advisories for org.apache.logging.log4j:log4j-core
- MediumCVE-2026-34479Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters · 10 Apr 2026
- MediumCVE-2026-34478Apache Log4j Core: log injection in `Rfc5424Layout` due to silent configuration incompatibility · 10 Apr 2026
- MediumCVE-2026-34477Apache Log4j Core: `verifyHostName` attribute silently ignored in TLS configuration · 10 Apr 2026
- MediumCVE-2025-68161Apache Log4j does not verify the TLS hostname in its Socket Appender · 18 Dec 2025
- HighCVE-2023-26464Apache Log4j 1.x (EOL) allows Denial of Service (DoS) · 10 Mar 2023
- MediumCVE-2021-44832Improper Input Validation and Injection in Apache Log4j2 · 4 Jan 2022
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-34480
- Linkgithub.com/apache/logging-log4j2/pull/4077
- Packagegithub.com/apache/logging-log4j2
- Linklists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhb
- Linklogging.apache.org/cyclonedx/vdr.xml
- Linklogging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout
- Linklogging.apache.org/security.html#CVE-2026-34480
- Linkwww.openwall.com/lists/oss-security/2026/04/10/9
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.