# Spring Security SAML2 Service Provider: Decryption Oracle Vulnerability from Unsigned SAML Response and Logout Payloads

Advisory record · `GHSA-ww38-37g9-m3q3`

- **Identifiers:** `GHSA-ww38-37g9-m3q3` · `CVE-2026-41694`
- **State:** Confirmed
- **Severity:** CVSS 3.7 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-347](https://cwe.mitre.org/data/definitions/347.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 10 Jun 2026
- **Updated:** 12 Aug 2026
- **Reviewed by a person:** No

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

## Affected packages

- `org.springframework.security:spring-security-saml2-service-provider` (Maven): affected `>=7.0.0, <7.0.6 || >=6.5.0, <6.5.11 || >=6.4.0, <=6.4.16 || >=6.3.0, <=6.3.16 || >=5.8.0, <=5.8.25 || <=5.7.23`; fixed in `7.0.6`, `6.5.11`

## Machine-written summary

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

> Spring Security SAML2 Service Provider (org.springframework.security:spring-security-saml2-service-provider) versions 5.7.23 and earlier, 5.8.x through 5.8.25, 6.3.x through 6.3.16, 6.4.x through 6.4.16, 6.5.0 through 6.5.10, and 7.0.0 through 7.0.5 are affected. The library decrypts SAML Responses and parts of LogoutRequests and LogoutResponses without checking a valid signature, so an attacker who can send crafted SAML payloads may be able to use the Service Provider as a decryption oracle. Upgrade to 7.0.6 or 6.5.11, or to the fixed version on your release line.

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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0015, the 4th percentile, on 10 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-ww38-37g9-m3q3)

## Sources

- [GitHub Advisory Database: GHSA-ww38-37g9-m3q3](https://github.com/advisories/GHSA-ww38-37g9-m3q3)
- [OSV: GHSA-ww38-37g9-m3q3](https://osv.dev/vulnerability/GHSA-ww38-37g9-m3q3)
- <https://nvd.nist.gov/vuln/detail/CVE-2026-41694>
- <https://github.com/spring-projects/spring-security>
- <https://github.com/spring-projects/spring-security/releases/tag/6.5.11>
- <https://github.com/spring-projects/spring-security/releases/tag/7.0.6>
- <https://spring.io/security/cve-2026-41694>

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-ww38-37g9-m3q3>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-ww38-37g9-m3q3/>. Everything for agents: <https://agentprime.io/llms.txt>.