CVE-2026-34480: Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

Published Apr 10, 2026
·
Updated

Apache Log4j Core's XmlLayout

Other sources

Apache Log4j Core's XmlLayout, in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification, 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, 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.

GitHub

Affected Software

11 affected componentsFixes available
maven/org.apache.logging.log4j:log4j-core>=3.0.0-alpha1<3.0.0-beta3
3.0.0-beta3
maven/org.apache.logging.log4j:log4j-core>=2.0-alpha1<2.25.4
2.25.4
maven/org.apache.logging.log4j:log4j-core>=3.0.0-alpha1<=3.0.0-beta3
Apache Log4j>=2.0<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
Apache Log4j=3.0.0-beta3
IBM watsonx.data<=2.2- 2.3.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade maven/org.apache.logging.log4j:log4j-core to a version that resolves this vulnerability.

    Fixed in 3.0.0-beta3
  2. Upgrade

    Upgrade maven/org.apache.logging.log4j:log4j-core to a version that resolves this vulnerability.

    Fixed in 2.25.4
  3. Upgrade

    Upgrade Apache Log4j Core to a version that resolves this vulnerability.

    Fixed in 2.25.4Patch CVE-2026-34480

Event History

Apr 10, 2026
CVE Published
via MITRE·03:42 PM
Data Sourced
via MITRE·03:42 PM
DescriptionWeakness
Data Sourced
via Red Hat·04:02 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
RemedyAffected Software
Advisory Published
via GitHub·06:31 PM
Data Sourced
via GitHub·06:31 PM
DescriptionWeaknessAffected Software
May 9, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-34480?

The severity of CVE-2026-34480 is classified as important due to its potential to cause silent log event loss.

2

How do I fix CVE-2026-34480?

To fix CVE-2026-34480, upgrade to version 2.25.4 or later, or to 3.0.0-beta3.

3

What versions are affected by CVE-2026-34480?

CVE-2026-34480 affects Apache Log4j Core versions up to and including 2.25.3.

4

What is the impact of CVE-2026-34480?

The impact of CVE-2026-34480 is the silent loss of log events due to unescaped forbidden XML characters.

5

Is there a workaround for CVE-2026-34480?

There is no documented workaround for CVE-2026-34480; upgrading to a patched version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203