Unsafe Deserialization in org.springframework.security:spring-security-saml2-service-provider (CVE-2026-40993)
Summary
Vulnerability in org.springframework.security:spring-security-saml2-service-provider (CVE-2026-40993). Data can be tampered with by attackers. Mitigation: upgrade to 7.0.6 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-40993 has been found in org.springframework.security:spring-security-saml2-service-provider.
Data can be tampered with by attackers. CVSS score: 7.3/10.
What to do: upgrade org.springframework.security:spring-security-saml2-service-provider to 7.0.6 or later.
If unsure, ask your IT team or search "org.springframework.security:spring-security-saml2-service-provider CVE-2026-40993" on the vendor's site.
CVE-2026-40993 (org.springframework.security:spring-security-saml2-service-provider) — CWE-502 / CVSS v3 7.3
Attack vector: adjacent-network / no user interaction
Patched: 7.0.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Unsafe deserialization (CWE-502) exists in org.springframework.security:spring-security-saml2-service-provider.
Check the vendor advisory for the affected versions of org.springframework.security:spring-security-saml2-service-provider.
Severity: High (CVSS 7.3/10). Data can be tampered with by attackers.
Update to 7.0.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで org.springframework.security:spring-security-saml2-service-provider を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework.security:spring-security-saml2-service-provider to 7.0.6ステージング環境で 7.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web spring.io
- web github.com
- web github.com