This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
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.
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
June 10, 2026
July 23, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.springframework.security:spring-security-saml2-service-provider | 7.0.0 ... 7.0.5 (6 versions) | 7.0.6 | — |
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 131 total refreshes for this CVE.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41694
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.