Spring Security: Open Redirect via Unvalidated Post-Login Redirect URL Stored in CookieRequestCache

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-41706: 0.21% estimated exploitation activity in the next 30 days; percentile 11.36 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 by the source

10 Jun 2026, 00:31 UTC

Last modified by the source

12 Aug 2026, 16:17 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x2r2-rvhq-2mqv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-41706

Advisory: Spring Security: Open Redirect via Unvalidated Post-Login Redirect URL Stored in CookieRequestCache
IDs: CVE-2026-41706, GHSA-x2r2-rvhq-2mqv
Record: https://patchnext.com/advisories/cve-2026-41706 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework.security:spring-security-web 7.0.6, 6.5.11. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework.security:spring-security-web: affected >= 7.0.0, <= 7.0.5; >= 6.5.0, <= 6.5.10; >= 6.3.0, <= 6.3.16; >= 5.8.0, <= 5.8.25; <= 5.7.23; fixed in 6.5.11, 7.0.6

## Suggested inspection (read-only)
- Maven org.springframework.security:spring-security-web: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework.security:spring-security-web.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x2r2-rvhq-2mqv (GitHub-reviewed advisory GHSA-x2r2-rvhq-2mqv lists affected ranges: Maven org.springframework.security:spring-security-web >=7.0.0 =6.5.0 =6.3.0 =5.8.0 =0 <=5.7.23)

Commands are suggestions: review each one before running it.