# CVE-2025-41248: CVE-2025-41248: Spring Security authorization bypass for method security annotations on parameterized types

> Attackers can bypass method security annotations in generic superclasses, allowing unauthorized access to protected methods in applications using Spring Security.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 16 Sep 2025
- **Updated:** 18 Sep 2025
- **Also known as:** CLEANSTART-2026-VH43982, ECHO-697c-1fee-1fce, GHSA-8v5q-rhf3-jphm, MINI-cvv4-65j9-9rww, MINI-pw7g-28fq-86xj, MINI-r87v-5426-7q35, MINI-wcjp-xpmq-7599, ROOT-APP-MAVEN-CVE-2025-41248

## What is CVE-2025-41248?

CVE-2025-41248 is a high-severity missing authorization vulnerability in VMware Spring Security, published on 16 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Spring Security annotation detection mechanism may not correctly resolve annotations on methods within type hierarchies with a parameterized super type with unbounded generics. This can be an issue when using @PreAuthorize and other method security annotations, resulting in an authorization bypass.

Your application may be affected by this if you are using Spring Security's @EnableMethodSecurity feature.

You are not affected by this if you are not using @EnableMethodSecurity or if you do not use security annotations on methods in generic superclasses or generic interfaces.

This CVE is published in conjunction with  CVE-2025-41249 https://spring.io/security/cve-2025-41249 .

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-core` | Maven | From 6.4.0 | 6.4.10 |
| `org.springframework.security:spring-security-core` | Maven | From 6.4.0 | 6.4.10 |
| `org.springframework.security:spring-security-core` | Maven | From 6.5.0 | 6.5.4 |
| `org.springframework.security:spring-security-core` | Maven | From 6.5.0 | 6.5.4 |

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

Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 6.4.10 or 6.5.4.

## Is CVE-2025-41248 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41248 is a high-severity missing authorization vulnerability in VMware Spring Security, published on 16 Sep 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-41248 in the wild and no public exploit code.

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

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-41248/ (Markdown: https://insights.sbomify.com/CVE-2025-41248/index.md)
```

## Sources

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

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