CVE-2026-34479
The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/apache/logging-log4j2/pull/4078
- lists.apache.org/thread/gd0hp6mj17rn3kj279vgy4p7kd4zz5on
- logging.apache.org/cyclonedx/vdr.xml
- logging.apache.org/log4j/2.x/migrate-from-log4j1.html
- logging.apache.org/security.html#CVE-2026-34479
- www.openwall.com/lists/oss-security/2026/04/10/8
- nvd.nist.gov/vuln/detail/CVE-2026-34479
- github.com/advisories/GHSA-h383-gmxw-35v2
- nvd.nist.gov/vuln/detail/CVE-2026-34479
- cve.org/CVERecord?id=CVE-2026-34479
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.