Vulnerability

CVE-2026-40995

Medium· 5.4CVSS5.4EPSS0%

.rules3/5

X509AuthenticationProvider could issue a fully authenticated X509AuthenticationToken when a presented certificate mapped to UserDetails, without applying Spring Security's standard account lifecycle checks (disabled, locked, expired, or credentials-expired accounts). 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

54/100

Elevated

Severity

medium

CVSS

5.4

EPSS

Active

CVSS

v3.1via NVDOpen in FIRST calculator →

5.4/ 10MEDIUMCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Attack VectorNetworkExploitable remotely over the internet — no local access needed.
Attack ComplexityLowNo special conditions — exploit works reliably.
Privileges RequiredLowStandard user privileges sufficient.
User InteractionNoneFully automated — no victim action needed.
ScopeUnchangedImpact contained to the vulnerable component.
Confidentiality ImpactLowSome data disclosure; attacker doesn't fully control what.
Integrity ImpactLowSome data modification; attacker doesn't fully control extent.
Availability ImpactNoneNo availability impact.

EPSS

Exploit prediction · 30-day horizonFIRST.org →

0.02%

probability of exploitation in next 30 days

higher than 5% 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-40995. Vendors publish VEX (Vulnerability Exploitability eXchange) to assert per-product whether a CVE is actually exploitable in their distribution.

SSVCDefer

No exploitation, limited impact or prevalence

exploitation: none
automatable: no
impact: partial
mission: support

Lifecycle

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

References

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

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