CVE-2026-40993: Unfiltered Java Native Deserialization of SAML 2.0 Asserting Party Credentials BLOB Database Entry
An attacker with write permissions to the database table managed by JdbcAssertingPartyMetadataRepository (saml2assertingpartymetadata) may be able to store malicious serialized payloads in the columns containing the collection of verification or encryption credentials (verificationcredentials and encryptioncredentials, respectively).
Affected versions: Spring Security 7.0.0 through 7.0.5.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-40993?
CVE-2026-40993 has a severity rating of high, specifically 7.3 on the CVSS scale.
What vulnerability does CVE-2026-40993 represent?
CVE-2026-40993 represents a risk of unfiltered Java native deserialization of SAML 2.0 asserting party credentials.
How does an attacker exploit CVE-2026-40993?
An attacker exploits CVE-2026-40993 by storing malicious serialized payloads in the database table managed by JdbcAssertingPartyMetadataRepository.
What impact does CVE-2026-40993 have on Spring Security?
The impact of CVE-2026-40993 on Spring Security includes the potential for remote code execution and unauthorized access to sensitive data.
How do I fix CVE-2026-40993?
To fix CVE-2026-40993, ensure proper validation of serialized data and restrict write permissions to the affected database tables.