BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2025
CVE-2025-41254High confidence

Spring Framework STOMP CSRF Vulnerability

VMware · Spring Framework

4.3MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 38 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Medium, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.31% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs VMware Spring Framework and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: As exposure requiresRemediation target: Within 365 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 38 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 4 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelibspring-javaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelibspring-javaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelibspring-javaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelibspring-javaAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appslibspring-javaUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges8 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.springframework:spring-websocketECOSYSTEM: introduced 6.2.0; fixed 6.2.126.2.12OSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.springframework:spring-websocketECOSYSTEM: introduced 6.1.0; last affected 6.1.21Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.springframework:spring-websocketECOSYSTEM: introduced 6.0.0; last affected 6.0.23Not statedOSV record ↗aggregator derived · 10 Sep 2026
Mavenorg.springframework:spring-websocketECOSYSTEM: introduced 0; last affected 5.3.39Not statedOSV record ↗aggregator derived · 10 Sep 2026
mavenorg.springframework:spring-websocket>= 6.2.0, < 6.2.126.2.12GitHub advisory ↗github reviewed aggregator · 17 Oct 2025
mavenorg.springframework:spring-websocket>= 6.1.0, <= 6.1.21Not statedGitHub advisory ↗github reviewed aggregator · 17 Oct 2025
mavenorg.springframework:spring-websocket>= 6.0.0, <= 6.0.23Not statedGitHub advisory ↗github reviewed aggregator · 17 Oct 2025
mavenorg.springframework:spring-websocket<= 5.3.39Not statedGitHub advisory ↗github reviewed aggregator · 17 Oct 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2025-41254 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityorg.springframework/spring-core: Spring Framework STOMP CSRF Vulnerability
34 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • spring-core as a component of Logging Subsystem for Red Hat OpenShift
  • spring-core as a component of Red Hat AMQ Broker 7
  • spring-core as a component of Red Hat AMQ Clients
  • spring-core as a component of Red Hat build of Apache Camel - HawtIO 4
  • spring-core as a component of Red Hat build of Apache Camel for Spring Boot 4
  • spring-core-test as a component of Red Hat build of Apache Camel for Spring Boot 4
  • spring-core as a component of Red Hat build of OptaPlanner 8
  • spring-core as a component of Red Hat Data Grid 8
  • log4j as a component of Red Hat Enterprise Linux 8
  • log4j-jcl as a component of Red Hat Enterprise Linux 8
  • log4j-slf4j as a component of Red Hat Enterprise Linux 8
  • log4j-web as a component of Red Hat Enterprise Linux 8
Summary
A CSRF flaw has been discovered in the Spring Framework. Usage of the STOMP messaging protocol over a WebSocket based application may be vulnerable to a security bypass that allows an attacker to send unauthorized messages.
Remediation
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.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2025-34768

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 38 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

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.

What

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.

Why

The application accepts a state-changing browser request without a reliable anti-forgery check.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The application accepts a state-changing browser request without a reliable anti-forgery check.

How

An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Cross-Site Request Forgery (CSRF) → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
Required interaction required
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-352 ↗

CWE-352: Cross-Site Request Forgery (CSRF). 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.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.ILowIntegrity impact: A successful attack can cause a limited loss.ANoneAvailability impact: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-352
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1204Oracle Financial Services Applications: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Financial Services Applications ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-1203Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2026-0351Dell NetWorker (Third Party Components): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell NetWorker ausnutzen, um Angriffe zu starten, die die Integrität, Vertraulichkeit und Verfügbarkeit von Systemen beeinträchtigen.

Official advisory ↗
BSI · German · WID-SEC-2026-0871IBM Operational Decision Manager: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Operational Decision Manager ausnutzen, um Sicherheitsvorkehrungen zu umgehen, und um Dateien zu manipulieren.

Official advisory ↗
BSI · German · WID-SEC-2025-2320VMware Tanzu Spring Framework: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in VMware Tanzu Spring Framework ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20251022Security Bulletin 22 Oct 2025

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Oct 2025, published on 22 October 2025. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0326Multiples vulnérabilités dans les produits VMware

d?id=CVE-2025-40354 Référence CVE CVE-2025-40355 https://www.cve.org/CVERecord?id=CVE-2025-40355 Référence CVE CVE-2025-40356 https://www.cve.org/CVERecord?id=CVE-2025-40356 Référence CVE CVE-2025-40358 https://www.cve.org/CVERecord?id=CVE-2025-40358 Référence CVE CVE-2025-40360 https://www.cve.org/CVERecord?id=CVE-2025-40360 Référence CVE CVE-2025-40362 https://www.cve.org/CVERecord?id=CVE-2025-40362 Référence CVE CVE-2025-40363 https://www.cve.org/CVERecord?id=CVE-2025-40363 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4382 https://www.cve.org/CVERecord?id=CVE-2025-4382 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-4575 https://www.cve.org/CVERecord?id=CVE-2025-4575 Référence CVE CVE-2025-46392 https://www.cve.org/CVERecord?id=CVE-2025-46392 Référence CVE CVE-2025-46394 https://www.cve.org/CVERecord?id=CVE-2025-46394 Référence CVE CVE-2025-46727 https://www.cve.org/CVERecord?id=CVE-2025-46727 Référence CVE CVE-2025-4673 https://www.cve.org/CVERecord?id=CVE-2025-4673 Référence CVE CVE-2025-4674 https://www.cve.org/CVERecord?id=CVE-202

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0218Multiples vulnérabilités dans les produits VMware

ord?id=CVE-2025-40243 Référence CVE CVE-2025-40244 https://www.cve.org/CVERecord?id=CVE-2025-40244 Référence CVE CVE-2025-40245 https://www.cve.org/CVERecord?id=CVE-2025-40245 Référence CVE CVE-2025-40297 https://www.cve.org/CVERecord?id=CVE-2025-40297 Référence CVE CVE-2025-40346 https://www.cve.org/CVERecord?id=CVE-2025-40346 Référence CVE CVE-2025-40349 https://www.cve.org/CVERecord?id=CVE-2025-40349 Référence CVE CVE-2025-40351 https://www.cve.org/CVERecord?id=CVE-2025-40351 Référence CVE CVE-2025-4056 https://www.cve.org/CVERecord?id=CVE-2025-4056 Référence CVE CVE-2025-40909 https://www.cve.org/CVERecord?id=CVE-2025-40909 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-4435 https://www.cve.org/CVERecord?id=CVE-2025-4435 Référence CVE CVE-2025-4516 https://www.cve.org/CVERecord?id=CVE-2025-4516 Référence CVE CVE-2025-4517 https://www.cve.org/CVERecord?id=CVE-2025-4517 Référence CVE CVE-2025-45582 https://www.cve.org/CVERecord?id=CVE-2025-45582 Référence CVE CVE-2025-45768 https://www.cve.org/CVERecord?id=CVE-2025-457

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0029Multiples vulnérabilités dans VMware Tanzu Gemfire

De multiples vulnérabilités ont été découvertes dans VMware Tanzu Gemfire. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une injection de requêtes illégitimes par rebond (CSRF) et un contournement de la politique de sécurité.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1024Multiples vulnérabilités dans les produits VMware

De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0969Multiples vulnérabilités dans les produits VMware

rd?id=CVE-2025-4056 Référence CVE CVE-2025-40778 https://www.cve.org/CVERecord?id=CVE-2025-40778 Référence CVE CVE-2025-40780 https://www.cve.org/CVERecord?id=CVE-2025-40780 Référence CVE CVE-2025-40909 https://www.cve.org/CVERecord?id=CVE-2025-40909 Référence CVE CVE-2025-41232 https://www.cve.org/CVERecord?id=CVE-2025-41232 Référence CVE CVE-2025-41242 https://www.cve.org/CVERecord?id=CVE-2025-41242 Référence CVE CVE-2025-41244 https://www.cve.org/CVERecord?id=CVE-2025-41244 Référence CVE CVE-2025-41248 https://www.cve.org/CVERecord?id=CVE-2025-41248 Référence CVE CVE-2025-41249 https://www.cve.org/CVERecord?id=CVE-2025-41249 Référence CVE CVE-2025-41254 https://www.cve.org/CVERecord?id=CVE-2025-41254 Référence CVE CVE-2025-4138 https://www.cve.org/CVERecord?id=CVE-2025-4138 Référence CVE CVE-2025-4207 https://www.cve.org/CVERecord?id=CVE-2025-4207 Référence CVE CVE-2025-4287 https://www.cve.org/CVERecord?id=CVE-2025-4287 Référence CVE CVE-2025-4330 https://www.cve.org/CVERecord?id=CVE-2025-4330 Référence CVE CVE-2025-4373 https://www.cve.org/CVERecord?id=CVE-2025-4373 Référence CVE CVE-2025-43857 https://www.cve.org/CVERecord?id=CVE-2025-43857 Référence CVE CVE-2025-43859 https://www.cve.org/CVERecord?id=CVE-2025-43859 Référence CVE CVE-2025-43965 https://www.cve.org/CVERecord?id=CVE-2025-4

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0883Multiples vulnérabilités dans les produits Spring

De multiples vulnérabilités ont été découvertes dans les produits Spring. Elles permettent à un attaquant de provoquer une atteinte à la confidentialité des données et un contournement de la politique de sécurité.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Users of affected versions should upgrade to fixed releases: 6.2.12 (OSS), 6.1.24 (Commercial), and 5.3.46 (Commercial). No further mitigation steps are necessary.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
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.
04

Evidence and provenance

Published 16 Oct 2025 · Last source change 16 Oct 2025, 16:10 UTC · CWE-352 · Cross-Site Request Forgery (CSRF)

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2025-34768
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD not scheduled

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
ENISA EUVD · EUVD-2025-34768↗Vendor CSAF · Red Hat Product Security↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2025-41254 · cve.blacktree.nl