CVE-2026-41726

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-06-10. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

When an application opts into DelegatingDeserializer, a producer can grow the consumer's heap without bound by sending records with unique random spring.kafka.serialization.selector header values, eventually causing GC thrash and OutOfMemoryError.

Affected versions: Spring for Apache Kafka 4.0.0 through 4.0.5; 3.3.0 through 3.3.15; 3.2.0 through 3.2.13; 2.9.0 through 2.9.13; 2.8.0 through 2.8.11.

CVSS v3
6.5
EG Score
6.5(high)
EPSS
20.8%
KEV
Not listed

Published

June 10, 2026

Last Modified

June 27, 2026

Advisory Details (1)

Auto-updated Jun 12, 2026
No patch confirmed yet.
generic

CVE-2026-41726: In Spring for Apache Kafka, unbounded delegate cache keyed on user-controlled, potentially malicious selector header

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

Vendor Advisories for CVE-2026-41726(1)

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

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.springframework.kafka:spring-kafka1.0.0.RELEASE ... 2.8.9 (160 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 62× 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-07-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 02:23 UTCEPSS rescore
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-05 11:31 UTCEG score recompute
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 12:04 UTCEG score recompute
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-03 08:17 UTCEG score recompute
  10. 2026-07-02 06:15 UTCEG score recompute
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-07-01 07:14 UTCEG score recompute
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-30 08:18 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 09:23 UTCEG score recompute
  17. 2026-06-28 14:07 UTCEPSS rescore
  18. 2026-06-28 10:28 UTCEG score recompute
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-27 11:20 UTCEG score recompute
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 12:25 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-25 10:15 UTCEG score recompute
Show 37 more
  1. 2026-06-24 14:05 UTCEPSS rescore
  2. 2026-06-24 11:12 UTCEG score recompute
  3. 2026-06-23 21:33 UTCEPSS rescore
  4. 2026-06-23 12:14 UTCEG score recompute
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 13:18 UTCEG score recompute
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 14:22 UTCEG score recompute
  11. 2026-06-21 01:59 UTCEPSS rescore
  12. 2026-06-20 13:59 UTCEG score recompute
  13. 2026-06-19 19:25 UTCEPSS rescore
  14. 2026-06-19 15:00 UTCEG score recompute
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-18 16:01 UTCEG score recompute
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-17 17:06 UTCEG score recompute
  20. 2026-06-16 17:57 UTCEG score recompute
  21. 2026-06-16 17:52 UTCEPSS rescore
  22. 2026-06-15 18:52 UTCEG score recompute
  23. 2026-06-15 17:49 UTCEPSS rescore
  24. 2026-06-14 19:55 UTCEG score recompute
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-13 21:00 UTCEG score recompute
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 22:03 UTCEG score recompute
  30. 2026-06-11 23:07 UTCEG score recompute
  31. 2026-06-11 23:07 UTCGHSA enrichment
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-11 00:12 UTCEG score recompute
  34. 2026-06-11 00:12 UTCGHSA enrichment
  35. 2026-06-10 22:18 UTCEPSS rescore
  36. 2026-06-10 01:17 UTCEG score recompute
  37. 2026-06-10 01:17 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-41726?
CVE-2026-41726 is a medium vulnerability published on June 10, 2026. When an application opts into DelegatingDeserializer, a producer can grow the consumer's heap without bound by sending records with unique random spring.kafka.serialization.selector header values, eventually causing GC thrash and OutOfMemoryError. Affected versions: Spring for Apache Kafka 4.0.0…
When was CVE-2026-41726 disclosed?
CVE-2026-41726 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41726 actively exploited?
CVE-2026-41726 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41726?
CVE-2026-41726 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-41726?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41726, 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-41726

Explore →

Is Your Infrastructure Affected by CVE-2026-41726?

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

Start Free Scan →Browse All CVEs