dbcve.org
Spring SecurityFramework / library · VMware

CVE-2026-40993

HIGH · 7.2 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 7.0.5.1 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a unsafe deserialization vulnerability in Spring Security's JdbcAssertingPartyMetadataRepository. An attacker with database write access to the saml2_asserting_party_metadata table can inject malicious serialized Java objects into the verification_credentials or encryption_credentials columns. When Spring Security reads and deserializes these credentials, it could lead to remote code execution.

MitigationRestrict write access to the saml2_asserting_party_metadata table to trusted administrators only, and upgrade Spring Security to version 7.0.6 or later once the patch is available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring SecurityFramework / library
Affected:>= 7.0.0, < 7.0.5.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Security version
    Check your project dependencies (Maven pom.xml, Gradle build.gradle, or the spring-security-core JAR manifest) for the Spring Security version number
    Affected if The version is 7.0.0 through 7.0.5 (inclusive)
  2. Confirm JdbcAssertingPartyMetadataRepository usage
    Search your codebase for imports or references to org.springframework.security.saml2.provider.service.metadata.JdbcAssertingPartyMetadataRepository, or check if SAML2 asserting party metadata is configured via JdbcAssertingPartyMetadataRepository bean
    Affected if Your application uses JdbcAssertingPartyMetadataRepository to store SAML2 metadata in a database
  3. Verify saml2_asserting_party_metadata table exists
    Query your database for the presence of a table named saml2_asserting_party_metadata (or similar), or review your database schema initialization scripts
    Affected if The table exists and is being used by your application
  4. Check database write access to metadata table
    Review database user permissions or application database connection configuration to determine which entities can write to the asserting party metadata table
    Affected if Untrusted users or the application itself has write access to this table without strict administrative controls

You are affected if your Spring Security version is 7.0.0-7.0.5 AND you use JdbcAssertingPartyMetadataRepository with a database table that untrusted actors can write to.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.5.1 or later
Fixed in 7.0.5.1
Interim mitigation

Restrict write access to the saml2_asserting_party_metadata table to trusted administrators only, and upgrade Spring Security to version 7.0.6 or later once the patch is available.

Recommended fix High confidence

Spring Security 7.0.5.1

  1. 1. Locate the Spring Security dependency in your project's build configuration (pom.xml for Maven or build.gradle for Gradle)
  2. 2. Update the Spring Security version to 7.0.5.1 or later
  3. 3. For Maven, update the version in the <properties> section or dependency management, e.g., change <spring-security.version>7.0.5</spring-security.version> to <spring-security.version>7.0.5.1</spring-security.version>
  4. 4. For Gradle, update the version string, e.g., change implementation 'org.springframework.security:spring-security-core:7.0.5' to implementation 'org.springframework.security:spring-security-core:7.0.5.1'
  5. 5. Rebuild the project to ensure the new version is resolved
  6. 6. Run application tests to verify functionality after the upgrade
  7. 7. If using JdbcAssertingPartyMetadataRepository, verify the database schema is compatible with the updated library
Caveat Minimal breaking changes expected within 7.0.x patch releases; however, review Spring Security 7.0 release notes for any migration considerations from earlier major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Security Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,864.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data