CVE-2026-41732

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-06-10. a secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Additionally, an empty trusted-packages configuration fell back to trusting all packages rather than applying a safe default allow-list.

Affected versions: Spring for Apache Pulsar 2.0.0 through 2.0.5; 1.2.0 through 1.2.17; 1.1.0 through 1.1.17.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/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
Severity81% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

CVE-2026-41732: In Spring for Apache Pulsar, overly broad trusted-package matching in header mapper exposes JDK classes to deserialization

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

Vendor Advisories for CVE-2026-41732(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 14× in last 7d / 69× 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 123 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41732?
CVE-2026-41732 is a high vulnerability published on June 10, 2026. JsonPulsarHeaderMapper matched type headers against trusted packages using a prefix check, meaning that trusting any package implicitly trusted all of its subpackages. Additionally, an empty trusted-packages configuration fell back to trusting all packages rather than applying a safe default…
When was CVE-2026-41732 disclosed?
CVE-2026-41732 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41732 actively exploited?
CVE-2026-41732 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 72.7% of all scored CVEs.
What is the CVSS score of CVE-2026-41732?
CVE-2026-41732 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-41732?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41732, 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-41732

Explore →

Is Your Infrastructure Affected by CVE-2026-41732?

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

Start Free Scan →Browse All CVEs