Spring SecurityFramework / library · VMware
CVE-2026-41008
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 Authorization Server's authorization endpoint performs insufficient validation of the request_uri parameter. An attacker can craft a malicious authorization request containing an invalid request_uri and an arbitrary, unvalidated redirect_uri, which can lead to an Open Redirect vulnerability. Affected versions: Spring Security 7.0.0 through 7.0.5. Spring Authorization Server 1.5.0 through 1.5.7.
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 Authorization Server's authorization endpoint does not properly validate the request_uri parameter, allowing attackers to craft malicious authorization requests with an invalid request_uri and an arbitrary unvalidated redirect_uri. This enables an Open Redirect attack where the attacker can redirect users to malicious sites after authorization.
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
>= 7.0.0, < 7.0.5.1>= 1.5.0, < 1.5.7.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 installed Spring Security or Spring Authorization Server versionCheck your project's dependency management file (pom.xml, build.gradle, or similar) for spring-security.version or spring-authorization-server.version. Alternatively, examine the JAR file names in your deployment under the application's classpath.Affected if The version falls within >= 7.0.0 and < 7.0.5.1 for Spring Security, or >= 1.5.0 and < 1.5.7.1 for Spring Authorization Server.
-
Confirm Spring Security OAuth2 Authorization Server is in useLook for the presence of @EnableAuthorizationServer annotation on a configuration class, or check for spring-authorization-server dependency in your build configuration.Affected if The application uses Spring Authorization Server with the authorization endpoint enabled.
-
Verify the OAuth2 authorization endpoint is exposedCheck your application's security configuration for OAuth2 authorization endpoint mappings, typically at /oauth2/authorize. Inspect the deployed application's exposed endpoints via startup logs or actuator endpoints if enabled.Affected if The /oauth2/authorize endpoint is accessible and handles authorization requests.
-
Inspect request_uri parameter handlingReview custom RegisteredClientRepository or AuthorizationServerSettings configurations to see if request_uri validation logic is implemented. Check whether the default request_uri validation is being overridden.Affected if No custom request_uri validation is implemented, relying on the vulnerable default behavior.
Your environment is affected if it runs any version of Spring Security 7.0.0 through 7.0.5.0 or Spring Authorization Server 1.5.0 through 1.5.7.0 with the authorization endpoint enabled and accessible.
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 · scoped1.5.7.17.0.5.1
Upgrade Spring Security to version 7.0.6 or later and Spring Authorization Server to version 1.5.8 or later. Alternatively, implement strict server-side validation of both request_uri and redirect_uri parameters before processing authorization requests.
Spring Security 7.0.5.1+ or Spring Authorization Server 1.5.7.1+
- Upgrade Spring Security to version 7.0.5.1 or later if using Spring Security
- OR upgrade Spring Authorization Server to version 1.5.7.1 or later if using Spring Authorization Server
- If using both products, upgrade both to their respective fixed versions
- Update the version in your Maven pom.xml or Gradle build.gradle file
- Run your build to fetch the updated dependencies
- Test the OAuth2 authorization flow to verify the fix resolves the open redirect vulnerability
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-41008 — 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-41008 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