CVE-2026-59272

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

Score 6.8 from GitHub Security Advisory published 2026-08-27. a secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
31(Track)
EG Risk 31/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
Severity68% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

August 27, 2026

Last Modified

September 1, 2026

Advisory Details (1)

Auto-updated Aug 27, 2026
No patch confirmed yet.
generic

Log4j2 AmqpAppender disables TLS hostname verification by default

https://spring.io/security/cve-2026-59272

Vendor Advisories for CVE-2026-59272(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 64× 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.

  1. 2026-09-19 06:39 UTCEG score recompute
  2. 2026-09-19 06:39 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 04:23 UTCEG score recompute
  5. 2026-09-18 04:23 UTCGHSA enrichment
  6. 2026-09-17 19:31 UTCEPSS rescore
  7. 2026-09-17 02:07 UTCEG score recompute
  8. 2026-09-17 02:07 UTCGHSA enrichment
  9. 2026-09-16 14:08 UTCEPSS rescore
  10. 2026-09-16 05:15 UTCEPSS rescore
  11. 2026-09-15 23:51 UTCEG score recompute
  12. 2026-09-15 23:51 UTCGHSA enrichment
  13. 2026-09-15 03:11 UTCEPSS rescore
  14. 2026-09-14 21:35 UTCGHSA enrichment
  15. 2026-09-13 19:18 UTCEG score recompute
  16. 2026-09-13 19:18 UTCGHSA enrichment
  17. 2026-09-13 16:47 UTCEPSS rescore
  18. 2026-09-12 17:02 UTCEG score recompute
  19. 2026-09-12 17:02 UTCGHSA enrichment
  20. 2026-09-11 14:46 UTCEG score recompute
  21. 2026-09-11 14:46 UTCGHSA enrichment
  22. 2026-09-10 12:30 UTCEG score recompute
  23. 2026-09-10 12:30 UTCGHSA enrichment
  24. 2026-09-10 09:35 UTCEPSS rescore
  25. 2026-09-09 10:10 UTCEG score recompute
Show 39 more
  1. 2026-09-09 10:10 UTCGHSA enrichment
  2. 2026-09-08 22:01 UTCEPSS rescore
  3. 2026-09-08 07:54 UTCEG score recompute
  4. 2026-09-08 07:54 UTCGHSA enrichment
  5. 2026-09-07 16:01 UTCEPSS rescore
  6. 2026-09-07 05:36 UTCEG score recompute
  7. 2026-09-07 05:35 UTCGHSA enrichment
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-06 03:18 UTCEG score recompute
  10. 2026-09-06 03:18 UTCGHSA enrichment
  11. 2026-09-05 01:02 UTCEG score recompute
  12. 2026-09-05 01:02 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-03 22:46 UTCGHSA enrichment
  15. 2026-09-02 20:29 UTCEG score recompute
  16. 2026-09-02 20:29 UTCGHSA enrichment
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 15:58 UTCEG score recompute
  19. 2026-09-01 15:58 UTCGHSA enrichment
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 01:50 UTCGHSA enrichment
  23. 2026-08-30 23:35 UTCEG score recompute
  24. 2026-08-30 23:35 UTCGHSA enrichment
  25. 2026-08-30 19:17 UTCEPSS rescore
  26. 2026-08-30 01:22 UTCEPSS rescore
  27. 2026-08-29 21:19 UTCEG score recompute
  28. 2026-08-29 21:19 UTCGHSA enrichment
  29. 2026-08-28 21:42 UTCEPSS rescore
  30. 2026-08-28 19:03 UTCGHSA enrichment
  31. 2026-08-28 05:26 UTCEG score recompute
  32. 2026-08-28 05:26 UTCGHSA enrichment
  33. 2026-08-28 04:59 UTCEG score recompute
  34. 2026-08-28 04:59 UTCGHSA enrichment
  35. 2026-08-27 20:27 UTCEG score recompute
  36. 2026-08-27 20:27 UTCGHSA enrichment
  37. 2026-08-27 17:24 UTCEG score recompute
  38. 2026-08-27 16:46 UTCEG score recompute
  39. 2026-08-27 16:43 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59272?
CVE-2026-59272 is a medium vulnerability published on August 27, 2026. Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is exposed to man-in-the-middle interception of every log event. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier
When was CVE-2026-59272 disclosed?
CVE-2026-59272 was first published in the National Vulnerability Database on August 27, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59272 actively exploited?
CVE-2026-59272 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.1% of all scored CVEs.
What is the CVSS score of CVE-2026-59272?
CVE-2026-59272 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-59272?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59272, 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

Explore the affected products and dependency analysis for CVE-2026-59272

Explore →

Is Your Infrastructure Affected by CVE-2026-59272?

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

Start Free Scan →Browse All CVEs