Is org.apache.logging.log4j:log4j-core affected by CVE-2026-34480?

Maven org.apache.logging.log4j:log4j-core is affected in >=2.0-alpha1 =3.0.0-alpha1 <=3.0.0-beta3.

Is CVE-2026-34480 being exploited?

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

medium

CVE-2026-34480

Q: Is CVE-2026-34480 being exploited?

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

Maven · org.apache.logging.log4j:log4j-core

Summary

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

Severity: medium
EPSS: 0.9% (p54)
Also known as: GHSA-3pxv-7cmr-fjr4
Published: 2026-04-10

References

Related advisories

CVE-2021-45046 — critical · Maven/org.apache.logging.log4j:log4j-core
CVE-2021-44228 — critical · Maven/org.apache.logging.log4j:log4j-core
CVE-2026-34478 — medium · Maven/org.apache.logging.log4j:log4j-core
CVE-2026-34477 — medium · Maven/org.apache.logging.log4j:log4j-core
CVE-2025-68161 — medium · Maven/org.apache.logging.log4j:log4j-core

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.