CVE-2026-41003 — spring-security-saml2-ser…
HIGHCVE-2026-41003 is a high-severity (CVSS 7.6) Cross-site Scripting (XSS) vulnerability in org.springframework.security:spring-security-saml2-service-provider. A fix is available for org.springframework.security:spring-security-saml2-service-provider — see the affected versions and patch details below.
Unencoded HTML Outputs in Spring Security May Allow Cross-Site Scripting
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-41003.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-provider☕org.springframework.security:spring-security-saml2-service-providerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An attacker able to influence values in RelyingPartyRegistration may be able to run arbitrary code on HTML forms generated by Spring Security filters.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 7.0.0&&< 7.0.6 | 7.0.6org.springframework.security:spring-security-saml2-service-provider:7.0.6 |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.5.0&&< 6.5.11 | 6.5.11org.springframework.security:spring-security-saml2-service-provider:6.5.11 |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | ≥ 5.8.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-saml2-service-provider | all versions | No fix |
Affected Products
spring securityvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.security:spring-security-saml2-service-provider, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security:spring-security-saml2-service-provider to 7.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41003 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2026-41003 in your dependencies?
Find it across Maven, including transitive dependencies.