Skip to content
Fencer Vulns
critical 9.1

CVE-2025-41232 in the critical feed json

CVE-2025-41232: Spring Security authorization bypass for method security annotations on private methods

published 2025-05-21 17 mo ago modified 2026-06-17 4 mo ago also GHSA-9pp5-9c7g-4r83 , EUVD-2025-15999

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

Summary

Spring Security Aspects may not correctly locate method security annotations on private methods. This can cause an authorization bypass.

Your application may be affected by this if the following are true:

* You are using @EnableMethodSecurity(mode=ASPECTJ) and spring-security-aspects, and * You have Spring Security method annotations on a private method In that case, the target method may be able to be invoked without proper authorization.

You are not affected if:

* You are not using @EnableMethodSecurity(mode=ASPECTJ) or spring-security-aspects, or * You have no Spring Security-annotated private methods

Patch / fix

  • maven org.springframework.security:spring-security-aspects 6.4.6
  • maven org.springframework.security:spring-security-core 6.4.6
  • Spring Spring Security 6.4.6

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-41232 updated cvss 7.4

Spring-Security: Spring Security authorization bypass for method security annotations on private methods

  • Red Hat A-MQ Clients 2 spring-security-core Red Hat OpenShift Developer Tools and Services jenkins
    not affected: vulnerable code not present
  • Red Hat build of Apache Camel for Spring Boot 4 spring-security-core
    not affected: inline mitigations already exist
  • Red Hat build of Quarkus quarkus-bom Red Hat Data Grid 8 spring-security-core Red Hat Fuse 7 spring-security-core, org.apache.servicemix.bundles.spring-security-core Red Hat Integration Camel K 1 spring-security-core Red Hat JBoss Enterprise Application Platform 7 spring-security-core Red Hat JBoss Enterprise Application Platform 8 spring-security-core
    +4 more products
    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
    not affected: vulnerable code not present

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
total
Assessed
17 mo ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 9.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-aspects
>=6.4.0, <6.4.6
6.4.6
maven org.springframework.security:spring-security-core
>=6.4.0, <6.4.6
6.4.6

Affected products

  • Spring Spring Security

Classification

Weakness
  • CWE-693 Protection Mechanism Failure
Technology feeds

References

Sources

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.