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

> Attackers can bypass authorization checks on private methods when using AspectJ mode, potentially accessing restricted functionality.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** CLEANSTART-2026-RU90125, GHSA-9pp5-9c7g-4r83, MINI-7mgg-83cr-mcg5, MINI-ffh9-cvqg-2hcw, MINI-hrf6-vg44-7p3j, ROOT-APP-MAVEN-CVE-2025-41232

## What is CVE-2025-41232?

CVE-2025-41232 is a critical missing authorization vulnerability in Spring Security, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-41232?

4 open source packages ship an affected version, including org.springframework.security:spring-security-aspects and org.springframework.security:spring-security-core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-aspects` | Maven | From 6.4.0 | 6.4.6 |
| `org.springframework.security:spring-security-aspects` | Maven | From 6.4.0 | 6.4.6 |
| `org.springframework.security:spring-security-core` | Maven | From 6.4.0 | 6.4.6 |
| `org.springframework.security:spring-security-core` | Maven | From 6.4.0 | 6.4.6 |

## How do I fix CVE-2025-41232?

Upgrade org.springframework.security:spring-security-aspects to 6.4.6 or later.

## Is CVE-2025-41232 being exploited?

There is no known exploitation of CVE-2025-41232 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41232 and fix it if it is affected.

What it is: CVE-2025-41232 is a critical missing authorization vulnerability in Spring Security, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41232 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.springframework.security:spring-security-aspects (Maven): affected from 6.4.0; fixed in 6.4.6
- org.springframework.security:spring-security-aspects (Maven): affected from 6.4.0; fixed in 6.4.6
- org.springframework.security:spring-security-core (Maven): affected from 6.4.0; fixed in 6.4.6
- org.springframework.security:spring-security-core (Maven): affected from 6.4.0; fixed in 6.4.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41232/ (Markdown: https://insights.sbomify.com/CVE-2025-41232/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41232
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41232
- OSV: https://osv.dev/vulnerability/CVE-2025-41232

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41232/
Summaries are generated and may contain mistakes; the official description above is the record.