CVE-2026-40995

X.509 authentication bypasses Spring Security account checks

Published Jun 11, 2026 CVSS 3.1 · 5.4 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

X509AuthenticationProvider can generate a fully authenticated X509AuthenticationToken for any certificate that maps to a UserDetails object while skipping the standard Spring Security account lifecycle checks. This flaw is an authentication bypass (CWE-287) and permits an attacker to authenticate as a disabled, locked, expired, or credentials‑expired account, enabling unauthorized access to protected application resources.

Affected Systems

The vulnerability impacts multiple releases of 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. These versions are commonly used to provide security for applications that rely on Spring Web Services.

Risk and Exploitability

The CVSS score of 5.4 classifies the flaw as moderate in severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog, indicating no widespread exploitation has been reported. The attack vector is inferred: an attacker must obtain a certificate that the application maps to a UserDetails instance and must have network access to a service performing X509 authentication. While the flaw does not provide arbitrary code execution or domain‑wide privilege escalation, bypassing the account checks can expose sensitive APIs or data to an account that should have been blocked.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Web Services to the latest release that contains the fix for CVE‑2026‑40995
  • Configure the application to enforce standard account lifecycle checks (disabled, locked, expired, credentials‑expired) before accepting an X509AuthenticationToken, or disable X509 authentication if it is not required
  • Monitor authentication logs for unexpected authentication events and consider implementing intrusion detection mechanisms tailored to X509 authentication

Generated by OpenCVE AI on June 11, 2026 at 07:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-6mfm-98wv-32wm Spring Web Services: X.509 authentication bypasses Spring Security account checks
References
History
Type Values Removed Values Added
First Time appeared Broadcom
Broadcom spring Web Services
CPEs cpe:2.3:a:broadcom:spring_web_services:*:*:*:*:*:*:*:*
Vendors & Products Broadcom
Broadcom spring Web Services
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Web Services
Vendors & Products Spring
Spring spring Web Services
Type Values Removed Values Added
Description 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.
Title X.509 authentication bypasses Spring Security account checks
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jun 23, 2026, 7:48 PM
Reserved
Apr 16, 2026, 2:19 AM
Status
Analyzed
Published
Jun 11, 2026, 7:16 AM
Modified
Sep 4, 2026, 5:10 PM