CVE-2026-41706 — spring-security-web
MEDIUMCVE-2026-41706 is a medium-severity (CVSS 6.1) Open Redirect vulnerability in org.springframework.security:spring-security-web. A fix is available for org.springframework.security:spring-security-web — see the affected versions and patch details below.
Open Redirect When Using CookieRequestCache
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-41706.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-41706 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-web☕org.springframework.security:spring-security-webReal-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
Spring Security's CookieRequestCache and CookieServerRequestCache store the pre-authentication request URL in a browser cookie so that users can be redirected back to their intended destination after a successful login. In affected versions, the full absolute URL is stored in the cookie and is used without validation as the post-login redirect target.
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-web | ≥ 7.0.0&&< 7.0.6 | 7.0.6org.springframework.security:spring-security-web:7.0.6 |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 6.5.0&&< 6.5.11 | 6.5.11org.springframework.security:spring-security-web:6.5.11 |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-web | ≥ 5.8.0 | No fix |
| ☕Maven | org.springframework.security:spring-security-web | 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-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.security:spring-security-web to 7.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-41706 is resolved across your whole dependency graph.
Workarounds
Stop reflecting attacker-controlled destinations: resolve every redirect target against an allowlist of paths or hosts you own, prefer a server-side key over a full URL in the request, and reject absolute URLs entirely where the flow only ever needs a relative one.
Frequently Asked Questions
Is CVE-2026-41706 in your dependencies?
Find it across Maven, including transitive dependencies.