Is org.apache.logging.log4j:log4j-1.2-api affected by CVE-2026-34479?

Maven org.apache.logging.log4j:log4j-1.2-api is affected in >=2.7 =3.0.0-beta1 <=3.0.0-beta2.

Is CVE-2026-34479 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

medium

CVE-2026-34479

Q: Is CVE-2026-34479 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

Maven · org.apache.logging.log4j:log4j-1.2-api

Summary

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

Severity: medium
EPSS: 0.5% (p41)
Also known as: GHSA-h383-gmxw-35v2
Published: 2026-04-10

References

https://nvd.nist.gov/vuln/detail/CVE-2026-34479
https://github.com/apache/logging-log4j2/pull/4078
https://github.com/apache/logging-log4j2

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.