CVE-2026-34479
EUVD-2026-2140910.04.2026, 16:16
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: * Those using Log4j1XmlLayout directly in a Log4j Core 2 configuration file. * Those using the Log4j 1 configuration compatibility layer with org.apache.log4j.xml.XMLLayout specified as the layout class. 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.Enginsight
Affected Products (NVD)
| Vendor | Product | Version |
|---|---|---|
| apache | log4j | 2.7 ≤ 𝑥 < 2.25.4 |
| apache | log4j | 3.0.0:alpha1 |
| apache | log4j | 3.0.0:alpha1_rc1 |
| apache | log4j | 3.0.0:alpha1_rc2 |
| apache | log4j | 3.0.0:beta1 |
| apache | log4j | 3.0.0:beta2 |
𝑥
= Vulnerable software versions
openSUSE / SLES Releases
openSUSE Product | |||||||||
|---|---|---|---|---|---|---|---|---|---|
| log4j |
| ||||||||
| log4j-javadoc |
| ||||||||
| log4j-jcl |
| ||||||||
| log4j-slf4j |
|
References