CVE-2026-40996

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

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

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

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

Wss4jSecurityInterceptor defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default for validation RequestData. Inbound WS-Security decryption could therefore accept RSA PKCS#1 v1.5 (rsa-1_5) encrypted key material unless operators explicitly reconfigured the flag.

Affected versions: Spring Web Services 5.0.0 through 5.0.1; 4.1.0 through 4.1.3; 4.0.0 through 4.0.18; 3.1.0 through 3.1.8.

CVSS v3
4.8
EG Score
4.8(medium)
EG Risk
26(Track)
EG Risk 26/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
Severity48% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
2.9%
KEV
Not listed

Published

June 11, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

CVE-2026-40996: Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default

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

Vendor Advisories for CVE-2026-40996(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 9× in last 7d / 55× 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-24 14:17 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:11 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 23:31 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 21:34 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-14 22:38 UTCGHSA enrichment
  16. 2026-07-13 23:36 UTCGHSA enrichment
  17. 2026-07-13 22:30 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 06:13 UTCEPSS rescore
  20. 2026-07-12 22:46 UTCGHSA enrichment
  21. 2026-07-12 05:46 UTCEPSS rescore
  22. 2026-07-11 22:28 UTCGHSA enrichment
  23. 2026-07-11 08:27 UTCEPSS rescore
  24. 2026-07-10 23:38 UTCGHSA enrichment
  25. 2026-07-10 00:01 UTCGHSA enrichment
Show 61 more
  1. 2026-07-09 19:10 UTCEPSS rescore
  2. 2026-07-09 01:10 UTCGHSA enrichment
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-08 02:12 UTCGHSA enrichment
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-07 03:20 UTCGHSA enrichment
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 16:27 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-06 02:23 UTCEPSS rescore
  11. 2026-07-05 13:09 UTCGHSA enrichment
  12. 2026-07-04 13:42 UTCGHSA enrichment
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 14:51 UTCGHSA enrichment
  15. 2026-07-02 11:54 UTCGHSA enrichment
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 12:43 UTCGHSA enrichment
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 13:52 UTCGHSA enrichment
  20. 2026-06-29 15:02 UTCGHSA enrichment
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 16:11 UTCGHSA enrichment
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 17:20 UTCGHSA enrichment
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-26 18:29 UTCGHSA enrichment
  28. 2026-06-25 19:39 UTCGHSA enrichment
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-24 20:48 UTCGHSA enrichment
  32. 2026-06-24 14:05 UTCEPSS rescore
  33. 2026-06-23 21:33 UTCEPSS rescore
  34. 2026-06-23 18:25 UTCGHSA enrichment
  35. 2026-06-22 19:30 UTCGHSA enrichment
  36. 2026-06-22 14:25 UTCEPSS rescore
  37. 2026-06-22 14:25 UTCEPSS rescore
  38. 2026-06-21 20:38 UTCGHSA enrichment
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-20 21:45 UTCGHSA enrichment
  41. 2026-06-19 22:54 UTCGHSA enrichment
  42. 2026-06-19 19:25 UTCEPSS rescore
  43. 2026-06-19 00:01 UTCGHSA enrichment
  44. 2026-06-18 17:52 UTCEPSS rescore
  45. 2026-06-18 17:52 UTCEPSS rescore
  46. 2026-06-18 01:09 UTCGHSA enrichment
  47. 2026-06-17 17:53 UTCEPSS rescore
  48. 2026-06-17 02:18 UTCGHSA enrichment
  49. 2026-06-16 17:52 UTCEPSS rescore
  50. 2026-06-16 03:28 UTCGHSA enrichment
  51. 2026-06-15 17:49 UTCEPSS rescore
  52. 2026-06-15 04:37 UTCGHSA enrichment
  53. 2026-06-14 05:46 UTCGHSA enrichment
  54. 2026-06-13 23:00 UTCEPSS rescore
  55. 2026-06-13 06:54 UTCGHSA enrichment
  56. 2026-06-12 23:12 UTCEPSS rescore
  57. 2026-06-12 23:12 UTCEPSS rescore
  58. 2026-06-12 08:02 UTCGHSA enrichment
  59. 2026-06-11 14:00 UTCEPSS rescore
  60. 2026-06-11 09:11 UTCEG score recompute
  61. 2026-06-11 09:10 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-40996?
CVE-2026-40996 is a medium vulnerability published on June 11, 2026. Wss4jSecurityInterceptor defaulted allowRSA15KeyTransportAlgorithm to true, overriding Apache WSS4J's safer default for validation RequestData. Inbound WS-Security decryption could therefore accept RSA PKCS#1 v1.5 (rsa-1_5) encrypted key material unless operators explicitly reconfigured the flag.…
When was CVE-2026-40996 disclosed?
CVE-2026-40996 was first published in the National Vulnerability Database on June 11, 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-40996 actively exploited?
CVE-2026-40996 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40996?
CVE-2026-40996 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-40996?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40996, 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-40996

Explore →

Is Your Infrastructure Affected by CVE-2026-40996?

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

Start Free Scan →Browse All CVEs