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

Should you act?

Critical and remotely reachable

No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

• No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
• EPSS 0.6%, percentile 49: FIRST’s model estimates a 0.6% chance of exploitation activity in the next 30 days, higher than 49% of all scored CVEs (low). EPSS is a probability, not a verdict.
• Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
• Only applies if your dependency tree includes org.springframework.security:spring-security-aspects (Maven) >= 6.4.0, < 6.4.6, fixed in 6.4.6; org.springframework.security:spring-security-core (Maven) >= 6.4.0, < 6.4.6, fixed in 6.4.6. Check your lockfile, including transitive dependencies.

What it is

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

From the GitHub advisory

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

Weakness type: CWE-693.

Product: org.springframework.security:spring-security-aspects (Maven) · Assigned by: vmware · Published: 2025-05-21

Affected and fixed versions

Severity scores

• Attack vector: network (remotely reachable)
• Attack complexity: low
• Privileges required: none (no login)
• User interaction: none
• Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

• CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
• CISA SSVC assessment: exploitation none, automatable yes, technical impact total.
• FIRST EPSS (model of 2026-10-21): 0.62% probability of exploitation activity in the next 30 days; percentile 49.

Timeline

• 2025-05-21 — CVE record published by vmware
• 2025-05-21 — GitHub-reviewed advisory GHSA-9pp5-9c7g-4r83 published (critical)
• 2026-02-26 — CVE record last updated

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

1. GitHub Advisory GHSA-9pp5-9c7g-4r83 github.com
2. CVE.org record CVE-2025-41232 cve.org
3. NVD entry CVE-2025-41232 nvd.nist.gov

Other references from the CVE record and advisory

1. spring.io spring.io
2. github.com github.com
3. github.com github.com
4. github.com github.com

Critical Maven advisories · Today’s Security Digest