Server code execution via unfiltered credential deserialization
Published Jun 9, 2026 · Updated Jun 9, 2026
Unsafe Java deserialization in Spring Security 7.0.0 through 7.0.5 allows attackers with database write access to execute server code. JdbcAssertingPartyMetadataRepository reads the verification_credentials and encryption_credentials BLOB columns as serialized Java objects without filtering attacker-controlled payloads. Exploitation requires write permission to saml2_asserting_party_metadata and occurs when an application reads the poisoned row, enabling code execution in that server process.
Summary
What happened
Unsafe Java deserialization in Spring Security 7.0.0 through 7.0.5 allows attackers with database write access to execute server code. JdbcAssertingPartyMetadataRepository reads the verification_credentials and encryption_credentials BLOB columns as serialized Java objects without filtering attacker-controlled payloads. Exploitation requires write permission to saml2_asserting_party_metadata and occurs when an application reads the poisoned row, enabling code execution in that server process.
The record
- CVE
- CVE-2026-40993
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Spring
- Product
- Spring Security
- Classifications
- CWE-502
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0.0 <7.0.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo