Is CVE-2026-40993 exploited in the wild?

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

How severe is CVE-2026-40993?

High severity, with a CVSS score of 7.3, published 10 June 2026.

Which products and versions are affected?

org.springframework.security:spring-security-saml2-service-provider (Maven) >= 7.0.0, <= 7.0.5, ECOSYSTEM:introduced=7.0.0,fixed=7.0.6; VMware Spring Security 7.0.0 through 7.0.5, 7.0.0 to 7.0.5.

Is there a fix for CVE-2026-40993?

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-40993 attacked?

It is attacked from the adjacent network, in a software library.

Am I affected by CVE-2026-40993?

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-40993: VMware Spring Security deserialization in JdbcAssertingPartyMetadataRepository

Q: Is there a fix for CVE-2026-40993?

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.

Q: How is CVE-2026-40993 attacked?

It is attacked from the adjacent network, in a software library.

Q: Am I affected by CVE-2026-40993?

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-40993 · Severity: high · CVSS 7.3 · Published 2026-06-10

Spring Security is a framework used to secure Java-based applications. A vulnerability in its SAML2 service provider component could allow an attacker with administrative database access to execute malicious code. By tampering with specific database tables used for identity management, an attacker could compromise the integrity and availability of the application.

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

Quick answers

Is CVE-2026-40993 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40993 being exploited in the wild.
How severe is CVE-2026-40993?: High severity, with a CVSS score of 7.3, published 10 June 2026.
Which products and versions are affected?: org.springframework.security:spring-security-saml2-service-provider (Maven) >= 7.0.0, <= 7.0.5, ECOSYSTEM:introduced=7.0.0,fixed=7.0.6; VMware Spring Security 7.0.0 through 7.0.5, 7.0.0 to 7.0.5.
Is there a fix for CVE-2026-40993?: 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-40993 attacked?: It is attacked from the adjacent network, in a software library.
Am I affected by CVE-2026-40993?: 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 deserialization vulnerability exists in the JdbcAssertingPartyMetadataRepository component of Spring Security's SAML2 Service Provider. The root cause is the unsafe deserialization of data retrieved from the 'saml2_asserting_party_metadata' database table, specifically within the 'verification_credentials' and 'encryption_credentials' columns. An attacker with write permissions to these database tables can inject malicious serialized Java objects. When the application subsequently retrieves and deserializes this data, it could lead to remote code execution or other integrity impacts. This vulnerability is mitigated by the requirement for high-privileged database access and a complex attack configuration. Users should upgrade to Spring Security 7.0.6 or later.

Affected products

VMware Spring Security 7.0.0 to 7.0.5

Identifiers

CVE-2026-40993
GHSA-2q7c-5gjm-7q23

Timeline

2026-06-10: disclosed
2026-06-10: advisory
2026-08-12: patched: GitHub advisory updated with patch information

References

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