Vulnerability

CVE-2026-40994

High· 8.2CVSS8.2EPSS0%

.rules3/5

Wss4jSecurityInterceptor initialized its BSP (WS-I Basic Security Profile) compliance flag so that inbound validation disabled WSS4J BSP enforcement on RequestData. Services that validate WS-Security on the network could therefore accept messages that violate BSP rules, weakening protocol-level checks. 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.

Threat signal

82/100

High

Severity

high

CVSS

8.2

EPSS

Active

CVSS

v3.1via NVDOpen in FIRST calculator →

8.2/ 10HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredNoneUnauthenticated — no credentials needed.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactLowSome data disclosure; attacker doesn't fully control what.
Integrity ImpactHighTotal compromise of integrity — full data modification possible.
Availability ImpactNoneNo availability impact.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

0.03%

probability of exploitation in next 30 days

higher than 8% of all CVEs

2-day trend↑ 0pp

Low exploitation likelihood — defer if no other signals fire.

Vendor VEX

No VEX statements published for CVE-2026-40994. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCTrack

Total impact on non-trivial mission systems

exploitation: none
automatable: yes
impact: total
mission: support

Lifecycle

2026-06-11Published
2026-06-11Last modified1 source

References

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

No source-event history recorded yet. New revisions will appear here as ingestors re-fetch this CVE.