CVE-2025-41254VulnerabilityPublished 16 Oct 2025

CVE-2025-41254: VMware Spring Framework · Cross-Site Request Forgery (CSRF)

Affects VMware Spring FrameworkSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 6.3.0 : update VMware Spring Framework when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 6.3.0, 6.2.0, 6.1.0 +1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 16 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.springframework/spring-framework to 6.3.0, 6.2.0, 6.1.0 or 5.4.0.

Affected software

Product	Affected	Fixed in
Mavenorg.springframework/spring-framework`pkg:maven/org.springframework/spring-framework`Other threats	Affected >=5.3.0 <5.4.0 >=6.0.0 <6.1.0 >=6.1.0 <6.2.0 >=6.2.0 <6.3.0	Fixed in 5.4.0 6.1.0 6.2.0 6.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade all affected Spring Framework versions to the fixed releases: 6.2.12 for 6.2.x, 6.1.24 for 6.1.x, and 5.3.46 for 5.3.x. 2. Review and harden WebSocket and STOMP configurations to enforce strict origin checks and CSRF protections where applicable. 3. Implement Content Security Policy (CSP) headers to reduce the risk of malicious script execution that could facilitate CSRF attacks. 4. Educate users about phishing and social engineering risks to reduce successful user interaction exploitation. 5. Employ Web Application Firewalls (WAFs) with rules designed to detect and block suspicious WebSocket traffic patterns. 6. Conduct thorough security testing of applications using STOMP over WebSocket to identify and remediate any additional weaknesses. 7. Monitor application logs for unusual STOMP message activity that could indicate exploitation attempts. 8. For organizations unable to immediately upgrade, consider temporary mitigations such as disabling STOMP over WebSocket if not essential or restricting access to trusted networks.

Description

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.

Impact

For European organizations, the impact of CVE-2025-41254 primarily concerns the integrity of web applications using the Spring Framework with STOMP over WebSocket. Attackers could send unauthorized messages that may alter application behavior, potentially leading to unauthorized actions such as data manipulation, transaction tampering, or triggering unintended workflows. While confidentiality and availability are not directly impacted, the integrity compromise could result in business process disruptions, reputational damage, or regulatory compliance issues, especially in sectors like finance, healthcare, and government where data accuracy and process integrity are critical. Organizations relying on vulnerable Spring Framework versions in customer-facing or internal real-time messaging applications are at risk. The requirement for user interaction means phishing or social engineering could be used to facilitate attacks. The lack of authentication requirement lowers the barrier for attackers to exploit this vulnerability once a user is tricked into interaction. Given the widespread use of Spring Framework in Europe’s software ecosystem, the potential for impact is significant if unpatched.

Summary

CVE-2025-41254 is a Cross-Site Request Forgery (CSRF) vulnerability identified in the VMware Spring Framework, specifically impacting applications that use STOMP over WebSocket messaging. The vulnerability arises because the affected Spring Framework versions (5.3.0 to 5.3.45, 6.0.x up to 6.0.29, 6.1.0 to 6.1.23, and 6.2.0 to 6.2.11) do not adequately protect against unauthorized message sending via CSRF attacks. STOMP (Simple Text Oriented Messaging Protocol) over WebSocket is commonly used for real-time messaging in web applications. An attacker exploiting this vulnerability can craft malicious requests that, when executed by an authenticated user’s browser, send unauthorized STOMP messages to the server, potentially manipulating application state or triggering unintended actions. The CVSS 3.1 base score is 4.3 (medium), reflecting that the attack vector is network-based, requires no privileges, but does require user interaction (e.g., tricking a user into visiting a malicious page). The impact is limited to integrity, with no direct confidentiality or availability consequences. Users of affected versions are strongly advised to upgrade to these patched releases. The vulnerability was responsibly disclosed by Jannis Kaiser. No known exploits are currently in the wild, but the presence of a fix indicates the risk is recognized and should be addressed promptly.

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Oct 2025, 15:14 UTC

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats