Spring Framework STOMP over WebSocket applications may allow attackers to send unauthorized messages

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

EPSS

• CVE-2025-41254: 0.31% estimated exploitation activity in the next 30 days; percentile 24.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.

Published by the source

16 Oct 2025, 15:30 UTC

Last modified by the source

17 Oct 2025, 17:37 UTC

Source last checked

26 Oct 2026, 16:40 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7fch-4f2f-jcgm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-41254

Advisory: Spring Framework STOMP over WebSocket applications may allow attackers to send unauthorized messages
IDs: CVE-2025-41254, GHSA-7fch-4f2f-jcgm
Record: https://patchnext.com/advisories/cve-2025-41254 (revision 1, source checked 26 Oct 2026, 16:40 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: org.springframework:spring-websocket 6.2.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.springframework:spring-websocket: affected >= 6.2.0, < 6.2.12; >= 6.1.0, <= 6.1.21; >= 6.0.0, <= 6.0.23; <= 5.3.39; fixed in 6.2.12

## Suggested inspection (read-only)
- Maven org.springframework:spring-websocket: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.springframework:spring-websocket.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7fch-4f2f-jcgm (GitHub-reviewed advisory GHSA-7fch-4f2f-jcgm lists affected ranges: Maven org.springframework:spring-websocket >=6.2.0 =6.1.0 =6.0.0 =0 <=5.3.39)

Commands are suggestions: review each one before running it.