CVE-2026-40993

Spring Security SAML2 Service Provider is vulnerable to Deserialization of Untrusted Data via JdbcAssertingPartyMetadataRepository

An attacker with write permissions to the database table managed by JdbcAssertingPartyMetadataRepository (saml2_asserting_party_metadata) may be able to store malicious serialized payloads in the columns containing the collection of verification or encryption credentials (verification_credentials and encryption_credentials, respectively).

Affected versions:
Spring Security 7.0.0 through 7.0.5.

Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.

CVE-2026-40993 has a CVSS score of 7.3 (High). The vector is reachable from an adjacent network, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.0.6); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is CVE-2026-40993? CVE-2026-40993 is a high-severity insecure deserialization vulnerability in org.springframework.security:spring-security-saml2-service-provider (maven), affecting versions >= 7.0.0, <= 7.0.5. It is fixed in 7.0.6. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
2. How severe is CVE-2026-40993? CVE-2026-40993 has a CVSS score of 7.3 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.springframework.security:spring-security-saml2-service-provider are affected by CVE-2026-40993? org.springframework.security:spring-security-saml2-service-provider (maven) versions >= 7.0.0, <= 7.0.5 is affected.
4. Is there a fix for CVE-2026-40993? Yes. CVE-2026-40993 is fixed in 7.0.6. Upgrade to this version or later.
5. Is CVE-2026-40993 exploitable, and should I be worried? Whether CVE-2026-40993 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40993 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40993? Upgrade org.springframework.security:spring-security-saml2-service-provider to 7.0.6 or later.

Other vulnerabilities in org.springframework.security:spring-security-saml2-service-provider