Vulnerability in org.springframework.security:spring-security-core (CVE-2025-22223)
Summary
Vulnerability in org.springframework.security:spring-security-core (CVE-2025-22223). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 6.4.4 or later.
Original description
The description as published by the source.
Spring Security 6.4.0 - 6.4.3 may not correctly locate method security annotations on parameterized types or methods. This may cause an authorization bypass.
You are not affected if you are not using @EnableMethodSecurity, or you do not have method security annotations on parameterized types or methods, or all method security annotations are attached to target methods
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-2025-22223 has been found in org.springframework.security:spring-security-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade org.springframework.security:spring-security-core to 6.4.4 or later.
If unsure, ask your IT team or search "org.springframework.security:spring-security-core CVE-2025-22223" on the vendor's site.
CVE-2025-22223 (org.springframework.security:spring-security-core) — CWE-290
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 6.4.4 — 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.
A vulnerability (CWE-290) exists in org.springframework.security:spring-security-core.
Check the vendor advisory for the affected versions of org.springframework.security:spring-security-core.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 6.4.4.
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-core を使っているサービスとバージョンを洗い出す。
-
2Apply patch patch
Upgrade org.springframework.security:spring-security-core to 6.4.4ステージング環境で 6.4.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web spring.io