CVE-2026-40999: Spring WS SSRF via unvalidated WS-Addressing reply destinations
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: org.springframework.ws:spring-ws-core (Maven) 4.1.4, 5.0.2.
Low priority for now. Upgrade to org.springframework.ws:spring-ws-core (Maven) 4.1.4, 5.0.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 11, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.3% · 32th percentile
- CWE
- CWE-918
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · vmware
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| broadcom | spring web services | cpe:2.3:a:broadcom:spring_web_services |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
Spring Spring Web Services
- 5.0.0 and later · before 5.0.1.1affected
- 4.1.0 and later · before 4.1.3.1affected
- 4.0.0 and later · before 4.0.19affected
- 3.1.0 and later · before 3.1.9affected
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- broadcom spring web servicesbefore 3.1.9
- broadcom spring web services4.0.0 and later · before 4.0.19
- broadcom spring web services4.1.0 and later · before 4.1.3.1
- broadcom spring web services5.0.0 and later · before 5.0.1.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.ws:spring-ws-core | from 3.1.0 · up to and including 3.1.8 | — |
| Maven | org.springframework.ws:spring-ws-core | from 4.0.0 · up to and including 4.0.18 | — |
| Maven | org.springframework.ws:spring-ws-core | from 4.1.0 · before 4.1.4 | 4.1.4 |
| Maven | org.springframework.ws:spring-ws-core | from 5.0.0 · before 5.0.2 | 5.0.2 |
Same product
broadcom: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-3773Spring Web Services XML External Entity Injection (XXE)40Plan
- CVE-2026-40998Jaxp13 XPath XXE via StreamSource and SAXSource32Monitor
- CVE-2026-40994Wss4jSecurityInterceptor disables WS-I BSP validation by default32Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-40996Jun 11, 2026 · Inbound WS-Security allows RSA PKCS#1 v1.5 key transport by default19Monitor
- ← EarlierCVE-2026-40997Jun 11, 2026 · SOAP security faults leak Spring Security account state21Monitor
- Later →CVE-2026-41000Jun 11, 2026 · WSS4J validation does not use configured replay cache14Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.ws:spring-ws-core | 4.1.4 | Package registry (OSV) |
| Maven:org.springframework.ws:spring-ws-core | 5.0.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-918 · Server-Side Request Forgery (SSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.