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

Medium 6.9 Published Updated

Attackers can cause log event loss or malformed XML output in Apache Log4j by injecting forbidden characters, potentially disrupting log processing.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-34480?

CVE-2026-34480 is a medium-severity vulnerability in Apache Log4j Core, published on 10 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets 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 https://github.com/FasterXML/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.

Weakness: CWE-116

Which versions are affected by CVE-2026-34480?

4 open source packages ship an affected version, including org.apache.logging.log4j:log4j-core. It affects 1 product.

PackageAffectedFixed in
org.apache.logging.log4j:log4j-core MavenFrom 2.0-alpha12.25.4
org.apache.logging.log4j:log4j-core MavenFrom 2.0-alpha12.25.4
org.apache.logging.log4j:log4j-core MavenFrom 3.0.0-alpha1 to 3.0.0-beta3None
org.apache.logging.log4j:log4j-core MavenFrom 3.0.0-alpha1 to 3.0.0-beta3None

Products include Apache Log4j.

How do I fix CVE-2026-34480?

Upgrade org.apache.logging.log4j:log4j-core to 2.25.4 or later.

Is CVE-2026-34480 being exploited?

There is no known exploitation of CVE-2026-34480 in the wild and no public exploit code.

Sources

Also known as CLEANSTART-2026-BH90179, CLEANSTART-2026-GM49347, CLEANSTART-2026-JA22493, CLEANSTART-2026-JH04977, CLEANSTART-2026-OV82681, CLEANSTART-2026-YQ06926 and 102 more.

Is CVE-2026-34480 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free