CVE-2025-41254 — spring-websocket
MEDIUMCVE-2025-41254 is a medium-severity (CVSS 4.3) 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
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-41254 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-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.
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-41254 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2025-41254. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-41254 in your dependencies?
O3 Security finds CVE-2025-41254 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.