CVE-2025-22223 json
Spring Security Vulnerable to Authorization Bypass via Security Annotations
published 2025-03-24 19 mo ago modified 2026-08-07 3 mo ago also GHSA-hh3m-g4qj-4835 , EUVD-2025-7998
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- maven org.springframework.security:spring-security-core 6.4.4
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-22223 updated cvss 5.3
spring-security: authorization bypass via incorrectly locating method security annotations on parameterized types or methods
-
Red Hat Fuse 7 spring-security-core, org.apache.servicemix.bundles.spring-security-core Red Hat Integration Camel K 1 spring-security-coreaffected: no fix planned “Out of support scope”
-
Red Hat A-MQ Clients 2 spring-security-core Red Hat OpenShift Developer Tools and Services jenkins Red Hat build of Apache Camel for Spring Boot 4 spring-security-core Red Hat build of Quarkus quarkus-bom Red Hat Data Grid 8 spring-security-core Red Hat JBoss Enterprise Application Platform 7 spring-security-corenot affected: vulnerable code not present
+5 more productsfewer
Red Hat JBoss Enterprise Application Platform 8 spring-security-core Red Hat JBoss Enterprise Application Platform Expansion Pack spring-security-core Red Hat Process Automation 7 spring-security-core Red Hat Single Sign-On 7 spring-security-core Red Hat streams for Apache Kafka spring-security-core
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.springframework.security:spring-security-core | >=6.4.0, <6.4.4 |
6.4.4 |
Affected products
- Spring Spring Security
Classification
- Weakness
-
- CWE-290 Authentication Bypass by Spoofing
- Technology feeds
References
Sources
- CVE List CVE-2025-22223
- GitHub Advisory GHSA-hh3m-g4qj-4835
- NVD CVE-2025-22223
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.