Skip to content
Fencer Intel
medium 6.1

CVE-2026-41706 json

Open Redirect When Using CookieRequestCache

published 4mo ago modified last mo. also GHSA-x2r2-rvhq-2mqv , EUVD-2026-35896

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.springframework.security:spring-security-web 6.5.11, 7.0.6
  • Spring Spring Security 5.7.24, 5.8.26, 6.3.17, 6.4.17, 6.5.10.2, 7.0.5.1

Is CVE-2026-41706 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
4mo ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-web
>=7.0.0, <7.0.6
>=6.5.0, <6.5.11
>=6.3.0, <=6.3.16
>=5.8.0, <=5.8.25
<=5.7.23
7.0.6
6.5.11

Affected products

  • Spring Spring Security

Classification

Weakness
  • CWE-601 URL Redirection to Untrusted Site
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.