The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML 1.0 standard, producing malformed XML output. Conforming XML parsers are required to reject documents containing such characters with a fatal error, which may cause downstream log processing systems to drop or fail to index affected records.
Two groups of users are affected:
Users are advised to upgrade to Apache Log4j 1-to-Log4j 2 bridge version 2.25.4, which corrects this issue.
Note: The Apache Log4j 1-to-Log4j 2 bridge is deprecated and will not be present in Log4j 3. Users are encouraged to consult the Log4j 1 to Log4j 2 migration guide https://logging.apache.org/log4j/2.x/migrate-from-log4j1.html , and specifically the section on eliminating reliance on the bridge.
{
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/34xxx/CVE-2026-34479.json",
"cwe_ids": [
"CWE-116"
],
"cna_assigner": "apache"
}{
"source": [
"CPE_RANGE",
"CPE_STRING"
],
"cpe": [
"cpe:2.3:a:apache:log4j:*:*:*:*:*:*:*:*",
"cpe:2.3:a:apache:log4j:3.0.0:alpha1:*:*:*:*:*:*",
"cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*",
"cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*"
],
"extracted_events": [
{
"introduced": "2.7"
},
{
"fixed": "2.25.4"
},
{
"introduced": "3.0.0-alpha1"
},
{
"last_affected": "3.0.0-alpha1"
},
{
"introduced": "3.0.0-beta1"
},
{
"last_affected": "3.0.0-beta1"
},
{
"introduced": "3.0.0-beta2"
},
{
"last_affected": "3.0.0-beta2"
}
]
}