CVE-2025-41254: Spring Framework STOMP CSRF Vulnerability
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: spring.io
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
STOMP over WebSocket applications may be vulnerable to a security bypass that allows an attacker to send unauthorized messages. Affected Spring Products and VersionsSpring 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. MitigationUsers of affected versions should upgrade to the corresponding fixed version. Affected version(s)Fix versionAvailability6.2.x6.2.12OSS6.1.x6.1.24 Commercial https://enterprise.spring.io/ 6.0.xN/A Out of support https://spring.io/projects/spring-framework#support 5.3.x5.3.46 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary. CreditThis vulnerability was discovered and responsibly reported by Jannis Kaiser.
- weakness
- CWE-352: Cross-Site Request Forgery (CSRF)
- affected
- VMware Spring Framework
- versions
- No affected-version range in held sources.
- fixed in
- No fix version in held sources.
- fixed by package (from OSV advisories)
- org.springframework:spring-websocket (Maven): 6.2.12 GHSA-7fch-4f2f-jcgm
- later fixes (from OSV advisories)
- spring-websocket 6.2.12 is inside a range CVE-2026-41838 (GHSA-q723-847q-5g8g) lists as affected. That advisory is fixed in 6.2.19.
- severity
- 4.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
- assigned by
- vmware
- published
- 2025-10-16
check us spring.io nvd.nist.gov
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 17 Oct 2025 | 0.0004 | |
| 22 Oct 2025 | 0.00043 | |
| 17 Nov 2025 | 0.00055 | |
| 28 Nov 2025 | 0.00076 | |
| 15 Jun 2026 | 0.00275 | scoring model v2026.06.15 |
| 23 Jun 2026 | 0.00286 | |
| 12 Jul 2026 | 0.00293 | |
| 16 Sep 2026 | 0.00314 |
23 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.00 on 2026-09-16 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-41254', '2026-10-29T23:59:59.999999Z', now());