vciy

CVE-2025-41234

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

RFD Attack via “Content-Disposition” Header Sourced from Request

CVE-2025-412343 of 4 sources documented this
16

rank 16 = 0 + 16 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00611  ·  without this subject the record ranks 16

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from the CNA  ·  without this subject the record ranks 0

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 16

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 16

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 16

Hindsight · the state

0.00611EPSSNOT IN KEVas of 2026-10-18
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-06-13, 490 days at 0.01, as of 2026-10-16. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running VMware Spring Framework? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch VMware Spring Framework

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachnetwork-reachable · low privileges required · user interaction required · high attack complexityreceipt
ImpactComplete confidentiality loss; partial integrity loss, with impact beyond the vulnerable componentreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')receipt
Published consequencesCWE-113: Integrity, Access Control: Modify Application Data, Gain Privileges or Assume Identitycwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in6.0.29; 6.1.21; 6.2.8receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA6.5 MEDIUMreceipt
Exploit probability0.00611 · top 52% of all CVEsreceipt
Assigned byvmwarereceipt
Recorded changes25 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productVMware Spring Frameworkreceipt
Fixed in6.0.29; 6.1.21; 6.2.8receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$21,900over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$21,900 = $4.99M incident cost x 0.7179585840212677 exposure x 0.00611 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Did this affect your environment?Answering needs an account.

Attack path

Network requestrequires low privileges, requires…VMware Spring FrameworkCWE-113 weaknessAdjacent componentsscope changeConfidentiality lossC:Hexploits CWE-113scope changedata compromise

What it is stated by the CNA

Description In Spring Framework, versions 6.0.x as of 6.0.5, versions 6.1.x and 6.2.x, an application is vulnerable to a reflected file download (RFD) attack when it sets a “Content-Disposition” header with a non-ASCII charset, where the filename attribute is derived from user-supplied input. Specifically, an application is vulnerable when all the following are true: * The header is prepared with org.springframework.http.ContentDisposition. * The filename is set via ContentDisposition.Builder#filename(String, Charset). * The value for the filename is derived from user-supplied input. * The application does not sanitize the user-supplied input. * The downloaded content o receipt

Read the rest of the CNA's description

f the response is injected with malicious commands by the attacker (see RFD paper reference for details). An application is not vulnerable if any of the following is true: * The application does not set a “Content-Disposition” response header. * The header is not prepared with org.springframework.http.ContentDisposition. * The filename is set via one of: * ContentDisposition.Builder#filename(String), or * ContentDisposition.Builder#filename(String, ASCII) * The filename is not derived from user-supplied input. * The filename is derived from user-supplied input but sanitized by the application. * The attacker cannot inject malicious content in the downloaded content of the response. Affected Spring Products and VersionsSpring Framework: * 6.2.0 - 6.2.7 * 6.1.0 - 6.1.20 * 6.0.5 - 6.0.28 * Older, unsupported versions are not affected MitigationUsers of affected versions should upgrade to the corresponding fixed version. Affected version(s)Fix versionAvailability6.2.x6.2.8OSS6.1.x6.1.21OSS6.0.x6.0.29 Commercial https://enterprise.spring.io/ No further mitigation steps are necessary. CWE-113 in `Content-Disposition` handling in VMware Spring Framework versions 6.0.5 to 6.2.7 allows remote attackers to launch Reflected File Download (RFD) attacks via unsanitized user input in `ContentDisposition.Builder#filename(String, Charset)` with non-ASCII charsets.

NVD's analysis a second authority

weakness
CWE-113
also scored by
security@vmware.com 6.5 CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N

check it yourself spring.io nvd.nist.gov nvd.nist.gov receipt

Movement the material steps

13 Jun 20250.0011
15 Jun 20260.00521 · scoring model v2026.06.15
16 Oct 20260.00611
Show all 25 observations
13 Jun 20250.0011
18 Jun 20250.00112
14 Jul 20250.00151
19 Aug 20250.00175
12 Oct 20250.00235
8 Nov 20250.00093
9 Nov 20250.00089
18 Nov 20250.00226
20 Nov 20250.00269
21 Nov 20250.00106
6 Jan 20260.00119
16 Jan 20260.00114
15 Feb 20260.00124
4 Mar 20260.00109
8 Apr 20260.0024
19 Apr 20260.00246
21 Apr 20260.0024
1 May 20260.00294
15 Jun 20260.00521
2 Jul 20260.00533
21 Jul 20260.00513
22 Jul 20260.00532
2 Sep 20260.00574
14 Sep 20260.00597
16 Oct 20260.00611

25 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00611Published2025-06-12Index as of2026-10-16

The record had been public for 1 year, 4 months when this index was last written.

Published 2025-06-12 receipt · Index as of 2026-10-16 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-41234.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.