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

Medium 6.5 Published Updated

Attackers can execute arbitrary code via reflected file download if applications use unsanitized user input for Content-Disposition filenames with non-ASCII charsets.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2025-41234?

CVE-2025-41234 is a medium-severity vulnerability in VMware Spring Framework, published on 12 Jun 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

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 of 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.

Weakness: CWE-113

Which versions are affected by CVE-2025-41234?

6 open source packages ship an affected version, including org.springframework:spring-web.

PackageAffectedFixed in
org.springframework:spring-web MavenFrom 6.0.5 to 6.0.23None
org.springframework:spring-web MavenFrom 6.0.5 to 6.0.23None
org.springframework:spring-web MavenFrom 6.1.06.1.21
org.springframework:spring-web MavenFrom 6.1.06.1.21
org.springframework:spring-web MavenFrom 6.2.06.2.8
org.springframework:spring-web MavenFrom 6.2.06.2.8

How do I fix CVE-2025-41234?

Upgrade org.springframework:spring-web to a fixed version for your release line: 6.1.21 or 6.2.8.

Is CVE-2025-41234 being exploited?

There is no known exploitation of CVE-2025-41234 in the wild and no public exploit code.

Sources

Also known as CLEANSTART-2026-FD72989, CLSA-2025-1754870569, ECHO-1c28-2269-e112, GHSA-6r3c-xf4w-jxjm, MINI-2562-h5j3-8j7p, MINI-3vxq-222r-9c34 and 5 more.

Is CVE-2025-41234 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free