Is CVE-2026-41694 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-41694 being exploited in the wild.

How severe is CVE-2026-41694?

Low severity, with a CVSS score of 3.7, published 10 June 2026.

Which products and versions are affected?

org.springframework.security:spring-security-saml2-service-provider (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.6; VMware 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.

Is there a fix for CVE-2026-41694?

Yes. org.springframework.security:spring-security-saml2-service-provider (Maven): upgrade to 7.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-41694 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-41694?

Check whether you run org.springframework.security:spring-security-saml2-service-provider (Maven) or VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-41694: VMware Spring Security decryption oracle in SAML implementation

CVE-2026-41694 · Severity: low · CVSS 3.7 · Published 2026-06-10

Spring Security, a widely used framework for securing Java applications, contains a vulnerability in its SAML2 login and logout processing. An attacker could potentially use the system to help decrypt sensitive information by sending specially crafted, unsigned messages. While this does not directly grant access to the system, it could allow an attacker to slowly uncover encrypted data, potentially compromising user privacy or security tokens.

Technologies: org.springframework.security:spring-security-saml2-service-provider (Maven), VMware Spring Security. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-41694 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-41694 being exploited in the wild.
How severe is CVE-2026-41694?: Low severity, with a CVSS score of 3.7, published 10 June 2026.
Which products and versions are affected?: org.springframework.security:spring-security-saml2-service-provider (Maven) ECOSYSTEM:introduced=7.0.0,fixed=7.0.6; VMware 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.
Is there a fix for CVE-2026-41694?: Yes. org.springframework.security:spring-security-saml2-service-provider (Maven): upgrade to 7.0.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-41694 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-41694?: Check whether you run org.springframework.security:spring-security-saml2-service-provider (Maven) or VMware Spring Security at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

org.springframework.security:spring-security-saml2-service-provider (Maven): upgrade to 7.0.6 or later

# set org.springframework.security:spring-security-saml2-service-provider to 7.0.6 in your pom.xml or build.gradle

Technical details

A decryption oracle vulnerability exists in the Spring Security SAML2 Service Provider component. The root cause is that the library attempts to decrypt elements within SAML Responses, LogoutRequests, and LogoutResponses before verifying a valid cryptographic signature. A remote, unauthenticated attacker can craft malicious SAML payloads to observe the application's decryption behavior. This allows the attacker to use the Service Provider as a decryption oracle to potentially recover plaintext from encrypted SAML elements. The vulnerability is addressed in versions 6.5.11 and 7.0.6.

Affected products

Spring Spring Security SAML2 Service Provider 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, 7.0.0 - 7.0.5

Identifiers

CVE-2026-41694
GHSA-ww38-37g9-m3q3

Timeline

2026-06-10: advisory
2026-06-10: disclosed
2026-08-12: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.