Skip to content
Fencer Intel
high 7.5

CVE-2025-41249 json

CVE-2025-41249: Spring Framework Annotation Detection Vulnerability

published last yr. modified last mo. also GHSA-jmp9-x22r-554x , EUVD-2025-29537

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

Summary

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 .

Patch / fix

  • maven org.springframework:spring-core 6.2.11
  • VMware Spring Framework 5.3.45, 6.1.23, 6.2.11

Is CVE-2025-41249 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-41249 updated cvss 7.5

org.springframework/spring-core: Spring Framework Annotation Detection Vulnerability

  • Red Hat AMQ Broker 7 spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat AMQ Clients spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat build of OptaPlanner 8 spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat Fuse 7 spring-core, org.springframework/spring-core org.springframework/spring-core
    affected: workaround, no fix planned “Will not fix”
  • Red Hat OpenShift Dev Spaces spring-core
    affected: workaround, no fix available
  • Red Hat Single Sign-On 7 spring-core, org.springframework/spring-core org.springframework/spring-core
    affected: workaround, no fix available, no fix planned “Will not fix”
  • Red Hat HawtIO HawtIO 4.3.0
    fixed: vendor fix RHSA-2025:22765
  • Red Hat build of Apache Camel 4.10.7 for Spring Boot 3.4.10
    fixed: vendor fix RHSA-2025:18028
  • Red Hat OpenShift Dev Spaces (RHOSDS) 3.24 devspaces 3.24-1760747489
    fixed: vendor fix RHSA-2025:19094
  • Red Hat Logging Subsystem for Red Hat OpenShift spring-core Red Hat Data Grid 8 spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat Enterprise Linux 8 log4j, resteasy, log4j-jcl, log4j-web, log4j-slf4j, resteasy-javadoc Red Hat Enterprise Linux 9 log4j, resteasy, log4j-jcl, log4j-slf4j, pki-resteasy-core, pki-resteasy-client, +2 more Red Hat JBoss Enterprise Application Platform 7 spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat JBoss Enterprise Application Platform 8 spring-core, org.springframework/spring-core org.springframework/spring-core
    +2 more products
    Red Hat JBoss Enterprise Application Platform Expansion Pack spring-core, org.springframework/spring-core org.springframework/spring-core Red Hat OpenShift Dev Spaces (RHOSDS) 3.24 devspaces 3.24-1759870356, devspaces 3.24-1759871071, devspaces 3.24-1759871505, devspaces 3.24-1759871621, devspaces 3.24-1759871872, devspaces 3.24-1760653610, +9 more
    not affected: vulnerable code not present
  • Red Hat Process Automation 7 spring-core, org.springframework/spring-core org.springframework/spring-core
    not affected: vulnerable code not in execute path

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
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.48% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
maven org.springframework:spring-core
>=5.3.0, <=5.3.44
>=6.0.0, <=6.1.22
>=6.2.0, <6.2.11
6.2.11

Affected products

  • VMware Spring Framework

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel 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.