CVE-2026-40999 — Spring WS SSRF via unvalidated WS-Addressing reply destinations
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+5
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — spring.io (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Broadcom Spring Web Services, Spring Spring Web Services).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the documented mitigations until a definitive fix is available.
- Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Broadcom | Spring Web Services | < 3.1.9≥ 4.0.0 and < 4.0.19≥ 4.1.0 and < 4.1.3.1≥ 5.0.0 and < 5.0.1.1 | Vulnerable | NIST National Vulnerability Database |
| Spring | Spring Web Services | ≥ 5.0.0 and < 5.0.1.1≥ 4.1.0 and < 4.1.3.1≥ 4.0.0 and < 4.0.19≥ 3.1.0 and < 3.1.9 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.6 | CVSS 3.1 | High | 3.9 | 4.0 | security@vmware.com via NIST National Vulnerability Database |
| 8.6 | CVSS 3.1 | High | — | — | vmware via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N (score shown at the top: security@vmware.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.43%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · spring/spring web services
- SSVC assessment updated
- Record published
- Fix documented
- CVSS changed · 8.6
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Low CVE-2026-41000 WSS4J validation does not use configured replay cache Jun 11, 2026
- High CVE-2026-40994 Wss4jSecurityInterceptor disables WS-I BSP validation by default Jun 11, 2026
- Medium CVE-2026-40995 X.509 authentication bypasses Spring Security account checks Jun 11, 2026
- Medium CVE-2026-40996 Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default Jun 11, 2026
- Medium CVE-2026-40997 SOAP security faults leak Spring Security account state Jun 11, 2026
- High CVE-2026-40998 Jaxp13 XPath XXE via StreamSource and SAXSource Jun 11, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-40999 is "Spring WS SSRF via unvalidated WS-Addressing reply destinations", rated High. It affects Spring Web Services (Broadcom); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.6 describes technical severity. EPSS 0.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.