rack
Affected
- introduced
0, fixed2.2.23(ecosystem)
Fixed versions
2.2.23
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-34763
Rack has a root directory disclosure via unescaped regex interpolation in Rack::Directory
Summary
Rack::Directory interpolates the configured root path directly into a regular expression when deriving the displayed directory path. If root contains regex metacharacters such as +, *, or ., the prefix stripping can fail and the generated directory listing may expose the full filesystem path in the HTML output.
Details
Rack::Directory::DirectoryBody#each computes the visible path using code equivalent to:
show_path = Utils.escape_html(path.sub(/\A#{root}/, ''))
Here, root is a developer-configured filesystem path. It is normalized earlier with File.expand_path(root) and then inserted directly into a regular expression without escaping.
Because the value is treated as regex syntax rather than as a literal string, metacharacters in the configured path can change how the prefix match behaves. When that happens, the expected root prefix is not removed from path, and the absolute filesystem path is rendered into the HTML directory listing.
Impact
If Rack::Directory is configured to serve a directory whose absolute path contains regex metacharacters, the generated directory listing may disclose the full server filesystem path instead of only the request-relative path.
This can expose internal deployment details such as directory layout, usernames, mount points, or naming conventions that would otherwise not be visible to clients.
Mitigation
Rack::Directory with a root path that contains regular expression metacharacters.Medium Basis: The source's own band: MODERATE
0, fixed 2.2.23 (ecosystem)2.2.23
The export has no generic command for this ecosystem.
3.0.0.beta1, fixed 3.1.21 (ecosystem)3.1.21
The export has no generic command for this ecosystem.
3.2.0, fixed 3.2.6 (ecosystem)3.2.6
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0