CVE-2026-34480

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 45% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
60%
KEV
Not listed

Published

April 10, 2026

Last Modified

April 24, 2026

Advisory Details (6)

Auto-updated Jun 15, 2026
Patch available. Sources: github_pr.
generic

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

http://www.openwall.com/lists/oss-security/2026/04/10/9
generic

Security :: Apache Logging Services

https://logging.apache.org/security.html#CVE-2026-34480
generic

Layouts :: Apache Log4j

https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout
generic
https://logging.apache.org/cyclonedx/vdr.xml
generic
https://lists.apache.org/thread/5x0hcnng0chhghp6jgjdp3qmbbhfjzhb
github_pr Patch Available

XmlLayout: replace invalid XML characters with U+FFFD

Patch available: apache/logging-log4j2 rel/2.25.4 (PR #4077 merged 2026-03-24)

https://github.com/apache/logging-log4j2/pull/4077

Vendor Advisories for CVE-2026-34480(10)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatlog4j-core2026-08-12redhat
redhatrhoai/odh-modelmesh-rhel9:17834438162026-07-21redhat
redhatlog4j-core-test2026-06-02redhat
redhatoffline-knowledge-portal/rhokp-rhel9:17799969992026-05-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
apache-log4j1.21.2.17-10, 1.2.17-10+deb11u1, 1.2.17-11——
apache-log4j22.13.3-1 ... 2.19.0-2 (17 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
apache-log4j1.21.2.17-11——
apache-log4j22.19.0-2——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
apache-log4j1.21.2.17-11——
apache-log4j22.19.0-2——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
apache-log4j1.21.2.17-11——
apache-log4j22.19.0-2——
Maven(1)
PackageVulnerable rangeFixed inDependents
org.apache.logging.log4j:log4j-core3.0.0-alpha1, 3.0.0-beta1, 3.0.0-beta2, 3.0.0-beta32.25.4—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 192 total refreshes for this CVE.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 05:06 UTCEPSS rescore
  16. 2026-09-02 14:12 UTCEPSS rescore
  17. 2026-09-02 06:44 UTCOSV refresh
  18. 2026-09-01 13:53 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 14:56 UTCEPSS rescore
  9. 2026-08-16 07:03 UTCEG score recompute
  10. 2026-08-16 07:03 UTCVendor advisory
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 18:21 UTCVendor advisory
  14. 2026-08-14 05:02 UTCEG score recompute
  15. 2026-08-14 05:02 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 09:20 UTCVendor advisory
  18. 2026-08-12 19:15 UTCEG score recompute
  19. 2026-08-12 19:15 UTCVendor advisory
  20. 2026-08-12 13:50 UTCEPSS rescore
  21. 2026-08-11 19:24 UTCEG score recompute
  22. 2026-08-11 19:24 UTCVendor advisory
  23. 2026-08-11 02:56 UTCEG score recompute
  24. 2026-08-11 02:56 UTCVendor advisory
  25. 2026-08-11 00:00 UTCEPSS rescore
  26. 2026-08-10 04:41 UTCVendor advisory
  27. 2026-08-09 16:35 UTCEG score recompute
  28. 2026-08-09 16:35 UTCVendor advisory
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 04:29 UTCEG score recompute
  31. 2026-08-09 04:29 UTCVendor advisory
  32. 2026-08-08 16:37 UTCEPSS rescore
  33. 2026-08-08 02:25 UTCEG score recompute
  34. 2026-08-08 02:25 UTCVendor advisory
  35. 2026-08-07 14:19 UTCEG score recompute
  36. 2026-08-07 14:19 UTCVendor advisory
  37. 2026-08-06 13:46 UTCEPSS rescore
  38. 2026-08-06 12:39 UTCVendor advisory
  39. 2026-08-05 23:40 UTCEG score recompute
  40. 2026-08-05 23:40 UTCVendor advisory
  41. 2026-08-05 19:17 UTCEPSS rescore
  42. 2026-08-04 15:10 UTCEPSS rescore
  43. 2026-08-04 10:38 UTCEPSS rescore
  44. 2026-08-03 21:55 UTCEG score recompute
  45. 2026-08-03 21:55 UTCVendor advisory
  46. 2026-08-03 10:36 UTCEPSS rescore
  47. 2026-08-03 01:53 UTCVendor advisory
  48. 2026-08-02 13:47 UTCEG score recompute
  49. 2026-08-02 13:47 UTCVendor advisory
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 01:30 UTCEPSS rescore
  54. 2026-07-27 14:13 UTCEPSS rescore
  55. 2026-07-26 14:54 UTCEPSS rescore
  56. 2026-07-26 14:54 UTCEPSS rescore
  57. 2026-07-25 14:18 UTCEPSS rescore
  58. 2026-07-25 14:18 UTCEPSS rescore
  59. 2026-07-24 14:17 UTCEPSS rescore
  60. 2026-07-24 14:17 UTCEPSS rescore
  61. 2026-07-23 14:18 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 03:09 UTCEG score recompute
  64. 2026-07-22 14:08 UTCEPSS rescore
  65. 2026-07-21 15:24 UTCEPSS rescore
  66. 2026-07-20 19:32 UTCOSV refresh
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:31 UTCEPSS rescore
  69. 2026-07-19 02:29 UTCEPSS rescore
  70. 2026-07-18 10:04 UTCEPSS rescore
  71. 2026-07-16 17:03 UTCEPSS rescore
  72. 2026-07-15 16:57 UTCEPSS rescore
  73. 2026-07-15 16:57 UTCEPSS rescore
  74. 2026-07-15 02:00 UTCEPSS rescore
  75. 2026-07-13 22:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-34480?
CVE-2026-34480 is a high vulnerability published on April 10, 2026. 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…
When was CVE-2026-34480 disclosed?
CVE-2026-34480 was first published in the National Vulnerability Database on April 10, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34480 actively exploited?
CVE-2026-34480 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 39.6% of all scored CVEs.
What is the CVSS score of CVE-2026-34480?
CVE-2026-34480 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-34480?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34480, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-34480

Explore →

Is Your Infrastructure Affected by CVE-2026-34480?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs