MediumGHSA-wvg4-6p58-3gh3CVE-2026-125110

Rack: Rack::Static header_rules bypass via dot-segment normalization mismatch

Published 10 Nov 2026 · Updated 10 Nov 2026

Is your project on an affected rack?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Rails or Ruby apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

rackRubyGems
Affected
<2.2.25
Fixed in
2.2.25
Update to the fixed version for your release line, for example:bundle update --conservative rack # Gemfile: '>= 2.2.25'
rackRubyGems
Affected
>=3.0.0 <3.1.23
Fixed in
3.1.23
Update to the fixed version for your release line, for example:bundle update --conservative rack # Gemfile: '>= 3.1.23'
rackRubyGems
Affected
>=3.2.0 <3.2.8
Fixed in
3.2.8
Update to the fixed version for your release line, for example:bundle update --conservative rack # Gemfile: '>= 3.2.8'

Details

Summary

Rack::Static normalizes the request path with Utils.clean_path_info when deciding which file to serve, but matches header_rules against a path that is only URL-decoded. A request containing dot segments, raw or percent-encoded, is served the normalized target file while the header rules for that file's location are not applied.

This allows an attacker to receive a protected static file without the security headers configured for it.

Details

Rack::Static#call computes the served path as Utils.clean_path_info(Utils.unescape_path(path)). Rack::Static#applicable_rules applies only Utils.unescape_path before testing string and regular expression rules. A request for /assets/../uploads/file.html or /assets/..%2fuploads/file.html is served as uploads/file.html, but the decoded path /assets/../uploads/file.html does not start with uploads, so a rule scoped to that directory never matches.

The fix for CVE-2026-34786 (GHSA-q4qf-9j86-f5mh) added URL decoding to rule matching but did not add dot segment normalization, so versions that include that fix remain affected.

Impact

Applications that use Rack::Static header_rules to attach security-relevant headers to particular paths or file types are affected. An unauthenticated attacker who knows the path of a protected file can request it through a dot segment path and receive it without those headers, for example without Content-Disposition: attachment or a restrictive Content-Security-Policy that prevents uploaded HTML from rendering inline. The file itself is served unchanged. Applications that do not use path-specific header_rules are not affected.

Mitigation

  • Update to a patched version of Rack in which header_rules are matched against the same normalized path used to serve the file.
  • Reject requests containing dot segments at a reverse proxy or application boundary.
  • Do not rely solely on Rack::Static header_rules to prevent inline rendering of untrusted uploads; serve them from a separate origin.

Credit

  • Reporter and Remediation developer

Is GHSA-wvg4-6p58-3gh3 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 rack, and gives you the command that fixes it.

More advisories for rack

  • HighCVE-2026-125111Rack: Multipart parsing allows DoS via unbounded scan buffer growth · 10 Nov 2026
  • LowCVE-2026-125108Rack: Multipart boundary ambiguity guard in Rack::Multipart::Parser can be bypassed with a quoted boundary value, allowing WAF bypass · 10 Nov 2026
  • MediumCVE-2026-125109Rack: Rack::Request#host_with_port (and #base_url / #url) return the raw invalid Host header — incomplete fix of CVE-2026-34835 · 10 Nov 2026
  • MediumCVE-2026-34835Rack::Request accepts invalid Host characters, enabling host allowlist bypass · 2 Apr 2026
  • MediumCVE-2026-34831Rack has Content-Length mismatch in Rack::Files error responses · 2 Apr 2026
  • MediumCVE-2026-34830Rack::Sendfile header-based X-Accel-Mapping regex injection enables unauthorized X-Accel-Redirect · 2 Apr 2026
All 54 advisories for rack

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.