CVE-2025-41234 is a medium-severity (CVSS 6.5) CWE-113 vulnerability in org.springframework:spring-web. A fix is available for org.springframework:spring-web — see the affected versions and patch details below.
Spring Framework vulnerable to a reflected file download (RFD)
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-41234.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-web☕org.springframework:spring-web☕org.springframework:spring-webReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-web | ≥ 6.2.0&&< 6.2.8 | 6.2.8org.springframework:spring-web:6.2.8 |
| ☕Maven | org.springframework:spring-web | ≥ 6.1.0&&< 6.1.21 | 6.1.21org.springframework:spring-web:6.1.21 |
| ☕Maven | org.springframework:spring-web | ≥ 6.0.5 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-web, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-web to 6.2.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-41234 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
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.Source: Red Hat security advisory for CVE-2025-41234 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2025-41234 in your dependencies?
Find it across Maven, including transitive dependencies.