CVE-2025-41249 is a high-severity (CVSS 7.5) CWE-285 vulnerability in org.springframework:spring-core. A fix is available for org.springframework:spring-core — see the affected versions and patch details below.
Spring Framework annotation detection mechanism may result in improper authorization
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-41249.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2025-41249 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.springframework:spring-core☕org.springframework:spring-core☕org.springframework:spring-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
The Spring Framework 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 if such annotations are used for authorization decisions.
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-41248 https://spring.io/security/cve-2025-41248 .
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-core | ≥ 5.3.0 | No fix |
| ☕Maven | org.springframework:spring-core | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-core | ≥ 6.2.0&&< 6.2.11 | 6.2.11org.springframework:spring-core:6.2.11 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of org.springframework:spring-core has shipped for CVE-2025-41249 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-41249 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-41249. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| HawtIO HawtIO 4.3.0 | org.springframework/spring-core | RHSA-2025:22765 |
| Red Hat build of Apache Camel 4.10.7 for Spring Boot 3.4.10 | org.springframework/spring-core | RHSA-2025:18028 |
| Red Hat OpenShift Dev Spaces (RHOSDS) 3.24 | devspaces/pluginregistry-rhel9:3.24-1760747489 | RHSA-2025:19094 |
Frequently Asked Questions
Is CVE-2025-41249 in your dependencies?
O3 Security finds CVE-2025-41249 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.