CVE-2026-34479

Apache Log4j 1 to Log4j 2 bridge: Silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters

Published Apr 10, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The Log4j1XmlLayout component fails to escape characters forbidden by XML 1.0, producing malformed XML logs. Conforming parsers reject such documents with a fatal error, causing downstream log processing to drop or fail to index these events. The defect does not provide arbitrary code execution but leads to loss of audit data, reducing the integrity of logs.

Affected Systems

Deployments using the Apache Log4j 1-to-Log4j 2 bridge are vulnerable. This includes configurations that employ Log4j1XmlLayout directly in Log4j Core 2, and those that use the Log4j 1 compatibility layer with org.apache.log4j.xml.XMLLayout. The vulnerability applies to any version prior to the corrected 2.25.4 release; no specific older version range is listed.

Risk and Exploitability

The CVSS score of 6.9 indicates medium severity, and the EPSS score of less than 1% suggests a low probability of exploitation. The CVE is not in the CISA KEV catalog. Based on the description, it is inferred that an attacker would need the ability to inject log entries containing XML‑forbidden characters, typically by influencing application input that is logged. No remote code execution or elevated privilege is required, so the risk of exploitation remains relatively low, but the loss of logs can impair incident response and compliance.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Apache Log4j 1-to-Log4j 2 bridge to version 2.25.4 or later.
  • If the bridge is no longer needed, remove it from the application to eliminate the vulnerability.
  • Disable Log4j1XmlLayout or the XMLLayout class when they are not required.
  • Verify that downstream log processing systems correctly handle escaped characters and monitor for missing events.
  • Follow the Log4j 1 to Log4j 2 migration guide to phase out the bridge entirely.

Generated by OpenCVE AI on April 14, 2026 at 02:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-h383-gmxw-35v2 Apache Log4j 1 to Log4j 2 bridge: silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters
History
Type Values Removed Values Added
CPEs 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:alpha1_rc1:*:*:*:*:*:*
cpe:2.3:a:apache:log4j:3.0.0:alpha1_rc2:*:*:*:*:*:*
cpe:2.3:a:apache:log4j:3.0.0:beta1:*:*:*:*:*:*
cpe:2.3:a:apache:log4j:3.0.0:beta2:*:*:*:*:*:*
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N'}

Type Values Removed Values Added
Weaknesses CWE-91
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Apache log4j
Vendors & Products Apache log4j
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Apache Log4j 1 to Log4j 2 bridge: Silent log event loss in Log4j1XmlLayout due to unescaped XML 1.0 forbidden characters
First Time appeared Apache
Apache log4j 1 2 Api
Weaknesses CWE-116
CPEs cpe:2.3:a:apache:log4j_1_2_api:*:*:*:*:*:*:*:*
Vendors & Products Apache
Apache log4j 1 2 Api
References
Metrics cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N'}

Weaknesses
  • CWE-116

    Improper Encoding or Escaping of Output

  • CWE-91

    XML Injection (aka Blind XPath Injection)

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Apr 10, 2026, 5:47 PM
Reserved
Mar 28, 2026, 2:06 PM
Status
Analyzed
Published
Apr 10, 2026, 4:16 PM
Modified
Oct 26, 2026, 9:10 PM
Severity
Moderate
Public date
Apr 10, 2026, 3:41 PM