Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2025-61780: Rack has Possible Information Disclosure Vulnerability

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.55% (FIRST EPSS).
  • 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: ruby-rack (Debian:11) 2.1.4-3+deb11u4; ruby-rack (Debian:12) 2.2.20-0+deb12u1; ruby-rack (Debian:13) 3.1.18-1~deb13u1.

Low priority for now. Upgrade to ruby-rack (Debian:11) 2.1.4-3+deb11u4; ruby-rack (Debian:12) 2.2.20-0+deb12u1; ruby-rack (Debian:13) 3.1.18-1~deb13u1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v3.1—No exploit Fix available
Published
Oct 10, 2025
Updated
Oct 19, 2026
EPSS
0.5% · 46th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

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.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-61780

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
rackrack

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.

EcosystemPackageAffected rangeFix
Debian:11ruby-rackbefore 2.1.4-3+deb11u42.1.4-3+deb11u4
Debian:12ruby-rackbefore 2.2.20-0+deb12u12.2.20-0+deb12u1
Debian:13ruby-rackbefore 3.1.18-1~deb13u13.1.18-1~deb13u1
Debian:14ruby-rackbefore 3.1.18-13.1.18-1
openSUSE:Leap 15.6rubygem-rackbefore 2.2.20-150000.3.34.12.2.20-150000.3.34.1
RubyGemsrackfrom 3.0 · before 3.1.183.1.18
RubyGemsrackfrom 3.2 · before 3.2.33.2.3
RubyGemsrackbefore 2.2.202.2.20
SUSE:Linux Enterprise High Availability Extension 15 SP3rubygem-rackbefore 2.2.20-150000.3.34.12.2.20-150000.3.34.1

Same product

rack: all records

Other 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 Parsing
    31Monitor
  • 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 al
    31Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2025-61771Oct 7, 2025 · Rack's multipart parser buffers large non‑file fields entirely in memory, enabling DoS (memory exhaustion)
    30Monitor
  • ← EarlierCVE-2025-61772Oct 7, 2025 · Rack's multipart parser buffers unbounded per-part headers, enabling DoS (memory exhaustion)
    30Monitor
  • Later →CVE-2025-61919Oct 10, 2025 · Rack is vulnerable to a memory-exhaustion DoS through unbounded URL-encoded body parsing
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:ruby-rack2.2.20-0+deb12u1 · Debian:12Package registry (OSV)
opensuse:rubygem-rack2.2.20-150000.3.34.1 · openSUSE:Leap 15.6Package registry (OSV)
RubyGems:rack2.2.20Package registry (OSV)
RubyGems:rack3.1.18Package registry (OSV)
RubyGems:rack3.2.3Package registry (OSV)
suse:rubygem-rack2.2.20-150000.3.34.1 · SUSE:Linux Enterprise High Availability Extension 15 SP3Package 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.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, 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

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

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records