Spring Framework vulnerable to a reflected file download (RFD)
Published 13 Jun 2025 · Updated 10 Sept 2026
Is your project on an affected org.springframework:spring-web?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=6.2.0 <6.2.8
- Fixed in
- 6.2.8
mvn versions:use-dep-version -Dincludes=org.springframework:spring-web -DdepVersion=6.2.8 -DforceVersion=true- Affected
- >=6.1.0 <6.1.21
- Fixed in
- 6.1.21
mvn versions:use-dep-version -Dincludes=org.springframework:spring-web -DdepVersion=6.1.21 -DforceVersion=true- Affected
- >=6.0.5 <=6.0.23
- Fixed in
- No fix released
Details
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), orContentDisposition.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
Mitigation
Users of affected versions should upgrade to the corresponding fixed version.
| Affected version(s) | Fix version | Availability | | - | - | - | | 6.2.x | 6.2.8 | OSS | | 6.1.x | 6.1.21 | OSS | | 6.0.x | 6.0.29 | Commercial |
No further mitigation steps are necessary.
Is GHSA-6r3c-xf4w-jxjm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.springframework:spring-web, and gives you the command that fixes it.
More advisories for org.springframework:spring-web
- MediumCVE-2026-41854Spring Framework Server-Side Request Forgery via UriComponentsBuilder · 9 Jun 2026
- MediumCVE-2024-38820Spring Framework DataBinder Case Sensitive Match Exception · 18 Oct 2024
- MediumCVE-2024-38809Spring Framework DoS via conditional HTTP request · 24 Sept 2024
- HighCVE-2024-22262Spring Framework URL Parsing with Host Validation · 16 Apr 2024
- HighCVE-2024-22259Spring Framework URL Parsing with Host Validation Vulnerability · 16 Mar 2024
- HighCVE-2024-22243Spring Web vulnerable to Open Redirect or Server Side Request Forgery · 23 Feb 2024
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.