CVE-2026-41694

SAML Payloads Decrypted Without Valid Signature

Published Jun 9, 2026 CVSS 3.1 · 3.7 Low EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability permits an attacker to decrypt SAML Responses, LogoutRequest, and LogoutResponse messages even when the payloads are not signed, a weakness classified as CWE-347 (Improper Restriction on Use of Cryptography). This flaw can lead to disclosure of authentication tokens or other sensitive data contained in the encrypted SAML assertions, thereby undermining the integrity of the Service Provider’s authentication flow. While the flaw does not enable direct code execution or privilege escalation, the confidential information revealed could be used to compromise user sessions.

Affected Systems

Spring Security library, versions 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, and 7.0.0 through 7.0.5, are affected.

Risk and Exploitability

The CVSS score of 3.7 indicates a medium severity, and EPSS is unavailable; the vulnerability is not listed in CISA KEV. Attackers would typically send crafted unsigned SAML payloads to SAML endpoints handled by Spring Security. Based on the description, the likely attack vector is over the network to the SAML assertion consumer or logout endpoint, using the Service Provider as a decryption oracle to learn the contents of encrypted messages that would otherwise remain confidential. No authentication bypass or code execution is directly tied to the flaw; the primary risk is data disclosure within the scope of reachable SAML messages.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring Security to the latest available release (e.g., 5.7.24+, 5.8.26+, 6.3.17+, 6.4.17+, 6.5.11+, or 7.0.6+), which removes the ability to decrypt unsigned SAML payloads.
  • If an immediate upgrade is not possible, enforce that all inbound SAML messages are signed and configure Spring Security to validate signatures before processing.
  • Apply network access controls to restrict exposure of SAML endpoints to trusted partners only.

Generated by OpenCVE AI on June 10, 2026 at 01:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-ww38-37g9-m3q3 Spring Security SAML2 Service Provider: Decryption Oracle Vulnerability from Unsigned SAML Response and Logout Payloads
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Security
CPEs cpe:2.3:a:vmware:spring_security:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Security
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Spring
Spring spring Security
Vendors & Products Spring
Spring spring Security
Type Values Removed Values Added
Description 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.
Title SAML Payloads Decrypted Without Valid Signature
Weaknesses CWE-347
References
Metrics cvssV3_1

{'score': 3.7, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N'}

Weaknesses
  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Jun 27, 2026, 9:25 PM
Reserved
Apr 22, 2026, 6:21 AM
Status
Analyzed
Published
Jun 10, 2026, 12:16 AM
Modified
Jul 23, 2026, 9:10 AM