CVE-2025-27610

Local File Inclusion in Rack::Static

HIGH
7.5
CVSS Score
Published: March 10, 2025 at 10:19 PM UTC
Updated: June 17, 2026 at 09:03 AM UTC
1 product affected across 1 vendorRack

Using rack by rack?

Get instant alerts when new vulnerabilities affect rack - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

Rack provides an interface for developing web applications in Ruby. Prior to versions 2.2.13, 3.0.14, and 3.1.12, `Rack::Static` can serve files under the specified `root:` even if `urls:` are provided, which may expose other files under the specified `root:` unexpectedly. The vulnerability occurs because `Rack::Static` does not properly sanitize user-supplied paths before serving files. Specifically, encoded path traversal sequences are not correctly validated, allowing attackers to access files outside the designated static file directory. By exploiting this vulnerability, an attacker can gain access to all files under the specified `root:` directory, provided they are able to determine then path of the file. Versions 2.2.13, 3.0.14, and 3.1.12 contain a patch for the issue. Other mitigations include removing usage of `Rack::Static`, or ensuring that `root:` points at a directory path which only contains files which should be accessed publicly. It is likely that a CDN or similar static file server would also mitigate the issue.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Rack· Rackrubygems
95%
v < 2.2.13v < 3.0.14v < 3.1.123.0.0 ≤ v < 3.0.143.1.0 ≤ v < 3.1.12
Affected range stops below 2.2.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.14, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.1.12, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-23

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card