# Spring Web Services: X.509 authentication bypasses Spring Security account checks

Advisory record · `GHSA-6mfm-98wv-32wm`

- **Identifiers:** `GHSA-6mfm-98wv-32wm` · `CVE-2026-40995`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-287](https://cwe.mitre.org/data/definitions/287.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 11 Jun 2026
- **Updated:** 21 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 11 Jun 2026, 09:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.springframework.ws:spring-ws-security` (Maven): affected `>=5.0.0, <5.0.2 || >=4.1.0, <4.1.4 || >=4.0.0, <=4.0.18 || >=3.1.0, <=3.1.8`; fixed in `5.0.2`, `4.1.4`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Spring Web Services (spring-ws-security) versions 5.0.0 through 5.0.1, 4.1.0 through 4.1.3, 4.0.0 through 4.0.18, and 3.1.0 through 3.1.8 are affected. The X509AuthenticationProvider could issue a fully authenticated token for a valid client certificate without applying account checks for disabled, locked, expired, or credentials-expired accounts, so a user whose account should be blocked could still authenticate. Upgrade to 5.0.2 or 4.1.4, or to a later release in the affected branch. The source gives no workaround.

Written 2 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`, from CNA (vmware)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:19 UTC: First seen by agentprime
- 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6mfm-98wv-32wm)

## Sources

- [GitHub Advisory Database: GHSA-6mfm-98wv-32wm](https://github.com/advisories/GHSA-6mfm-98wv-32wm)
- [OSV: GHSA-6mfm-98wv-32wm](https://osv.dev/vulnerability/GHSA-6mfm-98wv-32wm)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-40995>
- <https://github.com/spring-projects/spring-ws/commit/e5dc311359e14f5b25bcb33f20d43cc3513e9d10>
- <https://github.com/spring-projects/spring-ws>
- <https://spring.io/security/cve-2026-40995>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6mfm-98wv-32wm>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6mfm-98wv-32wm/>. Everything for agents: <https://agentprime.io/llms.txt>.