Spring SecurityFramework / library · VMware
CVE-2026-41706
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSpring 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSpring Security's CookieRequestCache and CookieServerRequestCache store the full absolute URL in an unencrypted browser cookie before authentication. After successful login, this stored URL is used as the redirect target without any validation, allowing attackers to craft malicious URLs that will redirect authenticated users to arbitrary sites (open redirect vulnerability).
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Spring SecurityFramework / library
< 5.7.24>= 5.8.0, < 5.8.26>= 6.3.0, < 6.3.17>= 6.4.0, < 6.4.17>= 6.5.0, < 6.5.10.2>= 7.0.0, < 7.0.5.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Spring Security versionLocate the spring-security-core JAR file in your classpath or build configuration (pom.xml, build.gradle, or in the deployed lib directory) and read its version attribute. Also check Maven/Gradle dependency trees for 'org.springframework.security:spring-security-core'.Affected if The installed version falls into any of these ranges: < 5.7.24; >= 5.8.0 and < 5.8.26; >= 6.3.0 and < 6.3.17; >= 6.4.0 and < 6.4.17; >= 6.5.0 and < 6.5.10.2; >= 7.0.0 and < 7.0.5.1
-
Verify CookieRequestCache or CookieServerRequestCache usageSearch your codebase for imports or references to 'org.springframework.security.web.savedrequest.CookieRequestCache' or 'org.springframework.security.web.savedrequest.CookieServerRequestCache'. Check your Spring Security configuration Java/XML files for bean definitions of type CookieRequestCache or CookieServerRequestCache.Affected if Your application uses CookieRequestCache or CookieServerRequestCache as the request cache implementation
-
Inspect request cache configurationExamine your Spring Security configuration (often in a SecurityFilterChain bean or extends WebSecurityConfigurerAdapter) for any .requestCache() configuration. Look for explicit CookieRequestCache or CookieServerRequestCache instantiation, or check if a custom RequestCache is defined that performs URL validation before redirect.Affected if No custom RequestCache with URL validation is configured, and the default cookie-based cache is in use
You are affected if your Spring Security version is within the vulnerable ranges AND you are using CookieRequestCache or CookieServerRequestCache without custom URL validation logic.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.7.245.8.266.3.17
Upgrade Spring Security to a patched version (5.7.24+, 5.8.26+, 6.3.17+, 6.4.17+, 6.5.11+, 7.0.6+) that validates the redirect URL before use. As a workaround, implement application-level validation of redirect targets or disable the cookie-based request cache if not needed.
Upgrade to the latest patch version in your current major.minor line: 5.7.24+, 5.8.26+, 6.3.17+, 6.4.17+, 6.5.11+, or 7.0.6+
- Identify your current Spring Security version in your build configuration (pom.xml, build.gradle, or similar)
- Determine which version branch you are on: 5.7.x, 5.8.x, 6.3.x, 6.4.x, 6.5.x, or 7.0.x
- For Spring Security 5.7.x: upgrade to version 5.7.24 or later
- For Spring Security 5.8.x: upgrade to version 5.8.26 or later
- For Spring Security 6.3.x: upgrade to version 6.3.17 or later
- For Spring Security 6.4.x: upgrade to version 6.4.17 or later
- For Spring Security 6.5.x: upgrade to version 6.5.11 or later
- For Spring Security 7.0.x: upgrade to version 7.0.6 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Spring Security
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-41706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-41706 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data