CVE-2026-41706: Open Redirect When Using CookieRequestCache
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: org.springframework.security:spring-security-web (Maven) 6.5.11, 7.0.6.
Low priority for now. Upgrade to org.springframework.security:spring-security-web (Maven) 6.5.11, 7.0.6 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 9, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-601
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · vmware
- 6.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring security | cpe:2.3:a:vmware:spring_security |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
Spring Spring Security
- 5.7.0 and later · before 5.7.24affected
- 5.8.0 and later · before 5.8.26affected
- 6.3.0 and later · before 6.3.17affected
- 6.4.0 and later · before 6.4.17affected
- 6.5.0 and later · before 6.5.10.2affected
- 7.0.0 and later · before 7.0.5.1affected
Affected versions · NVD (6)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vmware spring securitybefore 5.7.24
- vmware spring security5.8.0 and later · before 5.8.26
- vmware spring security6.3.0 and later · before 6.3.17
- vmware spring security6.4.0 and later · before 6.4.17
- vmware spring security6.5.0 and later · before 6.5.10.2
- vmware spring security7.0.0 and later · before 7.0.5.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.security:spring-security-web | from 5.8.0 · up to and including 5.8.25 | — |
| Maven | org.springframework.security:spring-security-web | from 6.3.0 · up to and including 6.3.16 | — |
| Maven | org.springframework.security:spring-security-web | from 6.5.0 · before 6.5.11 | 6.5.11 |
| Maven | org.springframework.security:spring-security-web | from 7.0.0 · before 7.0.6 | 7.0.6 |
| Maven | org.springframework.security:spring-security-web | up to and including 5.7.23 | — |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22978In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be…43Plan
- CVE-2023-34034Using "**" as a pattern in Spring Security configuration
for WebFlux creates a mismatch in pattern matching between Spring
Security and…40Plan
- CVE-2022-31692Spring Security, versions 5.7 prior to 5.7.5 and 5.6 prior to 5.6.9 could be susceptible to authorization rules bypass via forward or…40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-41003Jun 9, 2026 · Unencoded HTML Outputs in Spring Security May Allow Cross-Site Scripting21Monitor
- ← EarlierCVE-2026-41694Jun 9, 2026 · SAML Payloads Decrypted Without Valid Signature21Monitor
- Later →CVE-2026-47838Jun 9, 2026 · Unauthorized User Impersonation when Using X.509 Client Certificates32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.security:spring-security-web | 6.5.11 | Package registry (OSV) |
| Maven:org.springframework.security:spring-security-web | 7.0.6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.