CVE-2026-41694 json
SAML Payloads Decrypted Without Valid Signature
published 2026-06-09 5 mo ago modified 2026-08-12 2 mo ago also GHSA-ww38-37g9-m3q3 , EUVD-2026-35889
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
Since Spring Security SAML decrypts SAML Responses as well as elements of SAML LogoutRequests and LogoutResponses without requiring a valid signature, attackers may be able to craft these SAML payloads and use the Service Provider as a decryption oracle.
Affected versions: Spring Security 5.7.0 through 5.7.23; 5.8.0 through 5.8.25; 6.3.0 through 6.3.16; 6.4.0 through 6.4.16; 6.5.0 through 6.5.10; 7.0.0 through 7.0.5.
Patch / fix
- maven org.springframework.security:spring-security-saml2-service-provider 6.5.11, 7.0.6
- Spring Spring Security 5.7.24, 5.8.26, 6.3.17, 6.4.17, 6.5.10.2, 7.0.5.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.15% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.security:spring-security-saml2-service-provider | >=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 |
7.0.6 6.5.11 |
Affected products
- Spring Spring Security
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
- Technology feeds
References
Sources
- CVE List CVE-2026-41694
- GitHub Advisory GHSA-ww38-37g9-m3q3
- NVD CVE-2026-41694
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.