CVE-2026-34480
Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters
- State
- Published
- Severity
- 6.9 Medium
- Published
- Apr 10, 2026
- Updated
- Apr 10, 2026
- Reserved
- Mar 28, 2026
Description
Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets 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 https://github.com/FasterXML/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.
Scores
| CVSS | Score | Vector | Source |
|---|---|---|---|
| 4.0 | 6.9 Medium | 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 | apache |
Weaknesses
- CWE-116 Improper Encoding or Escaping of Output
Affected Products
| Product | Versions |
|---|---|
Apache Log4j CoreApache Software Foundation |
|
References
- https://github.com/apache/logging-log4j2/pull/4077patch
- https://logging.apache.org/security.html#CVE-2026-34480vendor-advisory
- https://logging.apache.org/cyclonedx/vdr.xmlvendor-advisory
- https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayoutrelated
- https://lists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhbvendor-advisory
- http://www.openwall.com/lists/oss-security/2026/04/10/9
Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.