BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-40999High confidence

Spring WS SSRF via unvalidated WS-Addressing reply destinations

Spring · Spring Web Services

8.6HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.43% for the current model date.

Compensating controls

  • Apply the linked authoritative mitigation while planning the permanent fix.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Spring Spring Web Services and falls inside the recorded affected range.
  2. Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Open-source package ranges8 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.springframework.ws:spring-ws-coreECOSYSTEM: introduced 5.0.0; fixed 5.0.25.0.2OSV record ↗aggregator derived · 21 Aug 2026
Mavenorg.springframework.ws:spring-ws-coreECOSYSTEM: introduced 4.1.0; fixed 4.1.44.1.4OSV record ↗aggregator derived · 21 Aug 2026
Mavenorg.springframework.ws:spring-ws-coreECOSYSTEM: introduced 4.0.0; last affected 4.0.18Not statedOSV record ↗aggregator derived · 21 Aug 2026
Mavenorg.springframework.ws:spring-ws-coreECOSYSTEM: introduced 3.1.0; last affected 3.1.8Not statedOSV record ↗aggregator derived · 21 Aug 2026
mavenorg.springframework.ws:spring-ws-core>= 5.0.0, <= 5.0.15.0.2GitHub advisory ↗github reviewed aggregator · 21 Aug 2026
mavenorg.springframework.ws:spring-ws-core>= 4.1.0, <= 4.1.34.1.4GitHub advisory ↗github reviewed aggregator · 21 Aug 2026
mavenorg.springframework.ws:spring-ws-core>= 4.0.0, <= 4.0.18Not statedGitHub advisory ↗github reviewed aggregator · 21 Aug 2026
mavenorg.springframework.ws:spring-ws-core>= 3.1.0, <= 3.1.8Not statedGitHub advisory ↗github reviewed aggregator · 21 Aug 2026
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-36209

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Mitigation available
01

What, why and how

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.

What

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.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The server follows an attacker-influenced destination, allowing requests to systems or services the attacker cannot reach directly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Server-Side Request Forgery (SSRF) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-918 ↗

CWE-918: Server-Side Request Forgery (SSRF). The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-918
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

CERT-FR · French · CERTFR-2026-AVI-1206Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-39824 Référence CVE CVE-2026-39892 https://www.cve.org/CVERecord?id=CVE-2026-39892 Référence CVE CVE-2026-40175 https://www.cve.org/CVERecord?id=CVE-2026-40175 Référence CVE CVE-2026-40192 https://www.cve.org/CVERecord?id=CVE-2026-40192 Référence CVE CVE-2026-40466 https://www.cve.org/CVERecord?id=CVE-2026-40466 Référence CVE CVE-2026-40682 https://www.cve.org/CVERecord?id=CVE-2026-40682 Référence CVE CVE-2026-40864 https://www.cve.org/CVERecord?id=CVE-2026-40864 Référence CVE CVE-2026-40973 https://www.cve.org/CVERecord?id=CVE-2026-40973 Référence CVE CVE-2026-40988 https://www.cve.org/CVERecord?id=CVE-2026-40988 Référence CVE CVE-2026-40999 https://www.cve.org/CVERecord?id=CVE-2026-40999 Référence CVE CVE-2026-41006 https://www.cve.org/CVERecord?id=CVE-2026-41006 Référence CVE CVE-2026-41007 https://www.cve.org/CVERecord?id=CVE-2026-41007 Référence CVE CVE-2026-41044 https://www.cve.org/CVERecord?id=CVE-2026-41044 Référence CVE CVE-2026-41254 https://www.cve.org/CVERecord?id=CVE-2026-41254 Référence CVE CVE-2026-41417 https://www.cve.org/CVERecord?id=CVE-2026-41417 Référence CVE CVE-2026-41603 https://www.cve.org/CVERecord?id=CVE-2026-41603 Référence CVE CVE-2026-41715 https://www.cve.org/CVERecord?id=CVE-2026-41715 Référence CVE CVE-2026-41839 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0739Multiples vulnérabilités dans les produits Spring

De multiples vulnérabilités ont été découvertes dans les produits Spring. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une atteinte à la confidentialité des données et une falsification de requêtes côté serveur (SSRF).

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-6847Spring 제품 보안 업데이트 권고

Spring Web Services에서 발생하는 Server-Side Request Forgery (SSRF) 취약점(CVE-2026-40999) [8][30]

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Mitigation available
Affected
Spring Web Services: 5.0.0 < 5.0.1.1, 4.1.0 < 4.1.3.1, 4.0.0 < 4.0.19, 3.1.0 < 3.1.9
Fixed
No fixed version is explicitly recorded in the structured CVE data.
Action
Apply the mitigation in the linked authoritative guidance while planning the vendor's permanent fix.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 11 Jun 2026 · Last source change 23 Jun 2026, 19:52 UTC · CWE-918 · Server-Side Request Forgery (SSRF)

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-36209
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Vendor guidanceAuthoritative vendor guidance changed: added mitigation: spring.io/cve-2026-40999; added remediation: spring.io/cve-2026-40999.
    Before
    no authoritative guidance recorded
    After
    mitigation: spring.io/cve-2026-40999 · remediation: spring.io/cve-2026-40999
    security@vmware.com ↗
  2. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    security@vmware.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Mitigation reference recorded
ENISA EUVD · EUVD-2026-36209↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-40999 · cve.blacktree.nl