CVE-2025-41254 — spring-websocket
MEDIUMCVE-2025-41254 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.springframework:spring-websocket. A fix is available for org.springframework:spring-websocket — see the affected versions and patch details below.
Spring Framework STOMP over WebSocket applications may allow attackers to send unauthorized messages
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-41254.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-websocket☕org.springframework:spring-websocket☕org.springframework:spring-websocket☕org.springframework:spring-websocketReal-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
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-websocket | ≥ 6.2.0&&< 6.2.12 | 6.2.12org.springframework:spring-websocket:6.2.12 |
| ☕Maven | org.springframework:spring-websocket | ≥ 6.1.0 | No fix |
| ☕Maven | org.springframework:spring-websocket | ≥ 6.0.0 | No fix |
| ☕Maven | org.springframework:spring-websocket | all versions | No fix |
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-websocket, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-websocket to 6.2.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-41254 is resolved across your whole dependency graph.
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.
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.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for CVE-2025-41254 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-41254 in your dependencies?
Find it across Maven, including transitive dependencies.