CVE-2026-34480 Details
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.
A vulnerability exists in Apache Log4j Core's XmlLayout, in versions up to and including 2.25.3. The layout fails to properly sanitize characters that are forbidden by the XML 1.0 specification, leading to the creation of invalid XML output. This issue arises whenever a log message or MDC value contains such characters. The consequences of this vulnerability vary depending on the StAX implementation in use. With the JRE's built-in StAX, forbidden characters are silently written to the output, resulting in malformed XML. Conforming parsers are required to reject such documents with a fatal error, which could cause downstream log-processing systems to discard the affected records. In contrast, alternative StAX implementations, such as Woodstox (a transitive dependency of the Jackson XML Dataformat module), throw an exception during the logging call, causing the log event to be lost and only reported to Log4j's internal status logger.
Users are advised to upgrade to Apache Log4j Core version 2.25.4, which addresses this vulnerability by sanitizing forbidden characters before generating XML output.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Apr 10, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| http://www.openwall.com/lists/oss-security/2026/04/10/9 | CVE | Mailing ListThird Party Advisory |
| https://github.com/apache/logging-log4j2/pull/4077 | [email protected] | Issue TrackingPatch |
| https://lists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhb | [email protected] | Mailing ListVendor Advisory |
| https://logging.apache.org/cyclonedx/vdr.xml | [email protected] | Product |
| https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout | [email protected] | Technical Description |
| https://logging.apache.org/security.html#CVE-2026-34480 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-116 | Improper Encoding or Escaping of Output | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| apache log4j | >= 2.0, < 2.25.4 3.0.0 alpha1 3.0.0 alpha1_rc1 3.0.0 alpha1_rc2 3.0.0 beta1 3.0.0 beta2 3.0.0 beta3 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 26, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 24, 2026 | Initial Analysis | [email protected] |
| Apr 10, 2026 | CVE Modified | CVE |
| Apr 10, 2026 | New CVE Received | [email protected] |