dbcve.org
Spring SecurityFramework / library · VMware

CVE-2026-41694

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 5.7.24 / 5.8.26 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Since Spring Security SAML decrypts SAML Responses as well as elements of SAML LogoutRequests and LogoutResponses without requiring a valid signature, attackers may be able to craft these SAML payloads and use the Service Provider as a decryption oracle. 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 confidence

Spring Security's SAML implementation decrypts SAML Responses, LogoutRequests, and LogoutResponses without requiring valid signatures, allowing attackers to craft malicious SAML payloads and abuse the Service Provider as a decryption oracle.

MitigationUpgrade Spring Security to a patched version (5.7.24+, 5.8.26+, 6.4.17+, 6.5.11+, or 7.0.6+) and ensure signature validation is enforced before decryption of all SAML messages.

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
Affected:>= 5.7.0, < 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.1

CVSS 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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Spring Security version in your dependencies
    Inspect your build file (pom.xml, build.gradle, gradle.lock) or the spring-security-core jar manifest for the exact Spring Security version number
    Affected if The installed version falls within any of these ranges: 5.7.0-5.7.23, 5.8.0-5.8.25, 6.3.0-6.3.16, 6.4.0-6.4.16, 6.5.0-6.5.10.1, or 7.0.0-7.0.5
  2. Confirm SAML2 login is enabled
    Search your Java configuration classes or XML configuration files for @EnableWebSecurity annotations with SAML2 login configuration, or look for RelyingPartyRegistration beans, or SAML-related XML elements in your security configuration
    Affected if Your application has SAML2 login or SAML service provider configuration present
  3. Verify SAML message processing is active
    Check if your application accepts SAML assertions, logout requests, or logout responses from an Identity Provider. Review your RelyingPartyRegistration configuration for the entities you trust
    Affected if Your application processes incoming SAML assertions or logout messages from external Identity Providers
  4. Inspect signature validation configuration
    Examine your SAML configuration for requiredSignatureValidation settings on your RelyingPartyRegistration. Look for configuration paths such as relyingPartyRegistration.withRelyingPartyRegistration(registration)->registration.signatureValidation(...)
    Affected if Signature validation on SAML messages is not explicitly required, or is set to optional/non-enforced in your configuration

You are affected if your application runs any unpatched Spring Security version within the affected ranges AND has SAML2 login or SAML service provider functionality configured to process SAML messages from Identity Providers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.7.24 / 5.8.26 / 6.3.17 or later
Fixed in 5.7.245.8.266.3.17
Interim mitigation

Upgrade Spring Security to a patched version (5.7.24+, 5.8.26+, 6.4.17+, 6.5.11+, or 7.0.6+) and ensure signature validation is enforced before decryption of all SAML messages.

Recommended fix High confidence

Spring Security 5.7.24, 5.8.26, 6.3.17, or 6.4.17 (depending on your current major version branch)

  1. 1. Identify your current Spring Security version by checking your project dependencies (pom.xml, build.gradle, or similar).
  2. 2. Determine which major version branch you are on (5.7.x, 5.8.x, 6.3.x, or 6.4.x).
  3. 3. For Spring Security 5.7.x: upgrade to version 5.7.24 or later.
  4. 4. For Spring Security 5.8.x: upgrade to version 5.8.26 or later.
  5. 5. For Spring Security 6.3.x: upgrade to version 6.3.17 or later.
  6. 6. For Spring Security 6.4.x: upgrade to version 6.4.17 or later.
  7. 7. Update your dependency management file (pom.xml or build.gradle) with the new version number.
  8. 8. Rebuild and test your application to ensure the upgrade does not break existing functionality.
Caveat Minor or patch upgrades typically have minimal breaking changes, but review the Spring Security release notes for any behavior changes between your current version and the target upgrade version.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Security Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41694 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41694 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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