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.
| Vendor | Product | Versions |
|---|---|---|
| apache | log4j | maven/org.apache.logging.log4j:log4j-core: >= 2.0-alpha1, < 2.25.4, maven/org.apache.logging.log4j:log4j-core: >= 3.0.0-alpha1, <= 3.0.0-beta3 |
Downstream vendors/products affected by this vulnerability
| Vendor | Product | Source | Confidence |
|---|---|---|---|
| apache | log4j | cert_advisory | 90% |
| maven | org.apache.logging.log4j:log4j-core | GHSA | 85% |
Updated description with new details about CVE-2026-34480 and noted that there is no available exploit.
Updated severity to MEDIUM, added new affected version 3.0.0-beta3, and marked exploit availability and active exploitation as true.
Initial creation
