CVE-2025-61780
Rack has Possible Information Disclosure Vulnerability
Description
Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely.
INFO
Published Date :
Oct. 10, 2025, 5:15 p.m.
Last Modified :
Oct. 30, 2025, 2:24 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | MEDIUM | [email protected] |
Solution
- Upgrade Rack to version 2.2.20, 3.1.18, or 3.2.3.
- Configure proxy to always set or strip headers.
- Disable sendfile in Rails applications if applicable.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-61780.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-61780 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-61780
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-61780 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-61780 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Oct. 30, 2025
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N Added CPE Configuration OR *cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:* versions up to (excluding) 2.2.20 *cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:* versions from (including) 3.0.0 up to (excluding) 3.1.18 *cpe:2.3:a:rack:rack:*:*:*:*:*:ruby:*:* versions from (including) 3.2.0 up to (excluding) 3.2.3 Added Reference Type GitHub, Inc.: https://github.com/rack/rack/commit/57277b7741581fa827472c5c666f6e6a33abd784 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/rack/rack/commit/7e69f65eefe9cd2868df9f9f3b0977b86f93523a Types: Patch Added Reference Type GitHub, Inc.: https://github.com/rack/rack/commit/fba2c8bc63eb787ff4b19bc612d315fda6126d85 Types: Patch Added Reference Type GitHub, Inc.: https://github.com/rack/rack/security/advisories/GHSA-r657-rxjc-j557 Types: Mitigation, Vendor Advisory -
New CVE Received by [email protected]
Oct. 10, 2025
Action Type Old Value New Value Added Description Rack is a modular Ruby web server interface. Prior to versions 2.2.20, 3.1.18, and 3.2.3, a possible information disclosure vulnerability existed in `Rack::Sendfile` when running behind a proxy that supports `x-sendfile` headers (such as Nginx). Specially crafted headers could cause `Rack::Sendfile` to miscommunicate with the proxy and trigger unintended internal requests, potentially bypassing proxy-level access restrictions. When `Rack::Sendfile` received untrusted `x-sendfile-type` or `x-accel-mapping` headers from a client, it would interpret them as proxy configuration directives. This could cause the middleware to send a "redirect" response to the proxy, prompting it to reissue a new internal request that was not subject to the proxy's access controls. An attacker could exploit this by setting a crafted `x-sendfile-type: x-accel-redirect` header, setting a crafted `x-accel-mapping` header, and requesting a path that qualifies for proxy-based acceleration. Attackers could bypass proxy-enforced restrictions and access internal endpoints intended to be protected (such as administrative pages). The vulnerability did not allow arbitrary file reads but could expose sensitive application routes. This issue only affected systems meeting all of the following conditions: The application used `Rack::Sendfile` with a proxy that supports `x-accel-redirect` (e.g., Nginx); the proxy did **not** always set or remove the `x-sendfile-type` and `x-accel-mapping` headers; and the application exposed an endpoint that returned a body responding to `.to_path`. Users should upgrade to Rack versions 2.2.20, 3.1.18, or 3.2.3, which require explicit configuration to enable `x-accel-redirect`. Alternatively, configure the proxy to always set or strip the header, or in Rails applications, disable sendfile completely. Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N Added CWE CWE-200 Added CWE CWE-441 Added CWE CWE-913 Added Reference https://github.com/rack/rack/commit/57277b7741581fa827472c5c666f6e6a33abd784 Added Reference https://github.com/rack/rack/commit/7e69f65eefe9cd2868df9f9f3b0977b86f93523a Added Reference https://github.com/rack/rack/commit/fba2c8bc63eb787ff4b19bc612d315fda6126d85 Added Reference https://github.com/rack/rack/security/advisories/GHSA-r657-rxjc-j557