CVE-2025-41254

CVE-2025-41254 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.springframework:spring-websocket (maven), affecting versions >= 6.2.0, < 6.2.12. It is fixed in 6.2.12.

Summary

STOMP over WebSocket applications may be vulnerable to a security bypass that allows an attacker to send unauthorized messages.

Affected Spring Products and Versions

Spring Framework:

  • 6.2.0 - 6.2.11
  • 6.1.0 - 6.1.23
  • 6.0.x - 6.0.29
  • 5.3.0 - 5.3.45
  • Older, unsupported versions are also affected.

Mitigation

Users of affected versions should upgrade to the corresponding fixed version.

Affected version(s)

Fix version Availability
6.2.x 6.2.12 OSS
6.1.x 6.1.24 Commercial https://enterprise.spring.io/
6.0.x N/A Out of support https://spring.io/projects/spring-framework#support
5.3.x 5.3.46 Commercial https://enterprise.spring.io/

No further mitigation steps are necessary.

CreditThis vulnerability was discovered and responsibly reported by Jannis Kaiser.

Impact

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2025-41254 has a CVSS score of 4.3 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.2.12); upgrading removes the vulnerable code path.

Affected versions

org.springframework:spring-websocket (>= 6.2.0, < 6.2.12) org.springframework:spring-websocket (>= 6.1.0, <= 6.1.21) org.springframework:spring-websocket (>= 6.0.0, <= 6.0.23) org.springframework:spring-websocket (<= 5.3.39)

Security releases

org.springframework:spring-websocket → 6.2.12 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade org.springframework:spring-websocket to 6.2.12 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2025-41254? CVE-2025-41254 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.springframework:spring-websocket (maven), affecting versions >= 6.2.0, < 6.2.12. It is fixed in 6.2.12. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
  2. How severe is CVE-2025-41254? CVE-2025-41254 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of org.springframework:spring-websocket are affected by CVE-2025-41254? org.springframework:spring-websocket (maven) versions >= 6.2.0, < 6.2.12 is affected.
  4. Is there a fix for CVE-2025-41254? Yes. CVE-2025-41254 is fixed in 6.2.12. Upgrade to this version or later.
  5. Is CVE-2025-41254 exploitable, and should I be worried? Whether CVE-2025-41254 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2025-41254 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2025-41254? Upgrade org.springframework:spring-websocket to 6.2.12 or later.

Other vulnerabilities in org.springframework:spring-websocket

Stop the waste.
Protect your environment with Kodem.