CVE-2026-40999

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.6EG
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.6Exploit: None knownExposed: 0

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

When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to.

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

Published

June 11, 2026

Last Modified

July 23, 2026

Advisory Details (1)

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

CVE-2026-40999: Spring WS SSRF via unvalidated WS-Addressing reply destinations

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

Vendor Advisories for CVE-2026-40999(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 18× in last 7d / 71× 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 129 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-40999?
CVE-2026-40999 is a high vulnerability published on June 11, 2026. When WS-Addressing is used with non-anonymous ReplyTo or FaultTo addresses, Spring WS may initiate outbound connections through configured WebServiceMessageSender instances to destinations taken directly from request headers without verifying that those destinations are safe to connect to. Affected…
When was CVE-2026-40999 disclosed?
CVE-2026-40999 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-40999 actively exploited?
CVE-2026-40999 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 69.1% of all scored CVEs.
What is the CVSS score of CVE-2026-40999?
CVE-2026-40999 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-40999?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40999, 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-40999

Explore →

Is Your Infrastructure Affected by CVE-2026-40999?

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