Rack has Possible Information Disclosure Vulnerability
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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Oct 10, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.6% · 44th percentile
- CWE
- CWE-200
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
21
Monitor
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.3
- CNA · GitHub_M
- 5.8
- 0.5 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| rack | rack | cpe:2.3:a:rack:rack |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rack rackbefore 2.2.20
- rack rack3.0.0 and later · before 3.1.18
- rack rack3.2.0 and later · before 3.2.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
rack rack
- < 2.2.20, >= 3.0, < 3.1.18, >= 3.2, < 3.2.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | ruby-rack | before 2.1.4-3+deb11u4 | 2.1.4-3+deb11u4 |
| Debian:12 | ruby-rack | before 2.2.20-0+deb12u1 | 2.2.20-0+deb12u1 |
| Debian:13 | ruby-rack | before 3.1.18-1~deb13u1 | 3.1.18-1~deb13u1 |
| Debian:14 | ruby-rack | before 3.1.18-1 | 3.1.18-1 |
| RubyGems | rack | from 3.0 · before 3.1.18 | 3.1.18 |
| RubyGems | rack | from 3.2 · before 3.2.3 | 3.2.3 |
| RubyGems | rack | before 2.2.20 | 2.2.20 |
| SUSE:Linux Enterprise High Availability Extension 15 SP3 | rubygem-rack | before 2.2.20-150000.3.34.1 | 2.2.20-150000.3.34.1 |
| SUSE:Linux Enterprise High Availability Extension 15 SP3 | rubygem-rack | before 2.2.20-150000.3.34.1 | 2.2.20-150000.3.34.1 |
Same product
rack: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-25126Rack ReDos in content type parsing (2nd degree polynomial)41Plan
- CVE-2024-26146Possible Denial of Service Vulnerability in Rack Header Parsing31Monitor
- CVE-2023-27530A DoS vulnerability exists in Rack <v3.0.4.2, <v2.2.6.3, <v2.1.4.3 and <v2.0.9.3 within in the Multipart MIME parsing code in which could al31Monitor
- CVE-2026-34827Rack: Algorithmic-Complexity DoS in Rack::Multipart::Parser30Monitor
- CVE-2026-34830Rack: Rack::Sendfile regex injection via HTTP_X_ACCEL_MAPPING header allows arbitrary file reads through nginx30Monitor
- CVE-2026-34829Rack: Denial of Service via Unbounded Multipart File Upload Without Content-Length30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:ruby-rack | 2.2.20-0+deb12u1 · Debian:12 | Package registry (OSV) |
| opensuse:rubygem-rack | 2.2.20-150000.3.34.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| RubyGems:rack | 2.2.20 | Package registry (OSV) |
| RubyGems:rack | 3.1.18 | Package registry (OSV) |
| RubyGems:rack | 3.2.3 | Package registry (OSV) |
| suse:rubygem-rack | 2.2.20-150000.3.34.1 · SUSE:Linux Enterprise High Availability Extension 15 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-200 · Exposure of Sensitive Information to an Unauthorized ActorCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
nvd-primary
Root cause
The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.
The bug in code
The whole CWE-200 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
{ "permissions": ["tabs", "<all_urls>"], "background": { "service_worker": "analytics.js" }}Fixed
{ "permissions": ["activeTab"], "host_permissions": ["https://yildiz.example/*"]}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ExcavationCAPEC-116likelihood: High · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- FootprintingCAPEC-169likelihood: High · Very Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- FingerprintingCAPEC-224likelihood: High · Very Low
- ICMP Echo Request PingCAPEC-285likelihood: Medium · Low
- TCP SYN ScanCAPEC-287Low
- Enumerate Mail Exchange (MX) RecordsCAPEC-290Low
ATT&CK techniques
- System Service DiscoveryT1007
- System Network Configuration DiscoveryT1016
- Remote System DiscoveryT1018
- System Owner/User DiscoveryT1033
- Masquerading: Match Legitimate Name or LocationT1036.005
- Network Service ScanningT1046
- System Network Connections DiscoveryT1049
- Process DiscoveryT1057
- Permission Groups DiscoveryT1069
- System Information DiscoveryT1082
- File and Directory DiscoveryT1083
- Account DiscoveryT1087
- Multi-Factor Authentication InterceptionT1111
- Peripheral Device DiscoveryT1120
- System Time DiscoveryT1124
- Access Token Manipulation:Token Impersonation/TheftT1134.001
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- github.com/rack/rack/commit/57277b7741581fa827472c5c666f6e6a33abd784
- github.com/rack/rack/commit/7e69f65eefe9cd2868df9f9f3b0977b86f93523a
- github.com/rack/rack/commit/fba2c8bc63eb787ff4b19bc612d315fda6126d85
- github.com/rack/rack/security/advisories/GHSA-r657-rxjc-j557
Vendor advisories and official records. Exploit/PoC links are deliberately left out.