Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2026-22860 is a high-severity Path Traversal (CWE-22) vulnerability in Rack Rack. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique File and Directory Discovery (T1083); ranked at the 49th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-22860 is a path traversal vulnerability in Rack, a modular Ruby web server interface. The issue affects the `Rack::Directory` component in versions prior to 2.2.22, 3.1.20, and 3.2.5. It stems from a flawed path check that relies on a string prefix match on the expanded path, enabling attackers to bypass the configured root directory. For example, a request like `/../root_example/` can escape the root if the target path begins with the root string, resulting in unauthorized directory listings outside the intended scope. The vulnerability is rated 7.5 on the CVSS 3.1 scale (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N) and maps to CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) and CWE-548 (Exposure of Information Through Directory Listing).
Remote attackers without authentication can exploit this vulnerability by sending specially crafted HTTP requests to a Rack application serving directory listings. Successful exploitation allows listing of directory contents beyond the configured root, potentially exposing sensitive files and information on the server filesystem. No user interaction is required, and the attack is straightforward due to low complexity and network accessibility.
The Rack security advisory (GHSA-mxw3-3hh2-x2mh) and the fixing commit (75c5745c286637a8f049a33790c71237762069e7) recommend upgrading to Rack versions 2.2.22, 3.1.20, or 3.2.5, which implement a corrected path normalization check to prevent root escapes.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7914
Vulnerability Data
Rack is a modular Ruby web server interface. Prior to versions 2.2.22, 3.1.20, and 3.2.5, `Rack::Directory`’s path check used a string prefix match on the expanded path. A request like `/../root_example/` can escape the configured root if the target path…
more
starts with the root string, allowing directory listing outside the intended root. Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.3.2
Mitigating Controls (NIST 800-53 r5) AI
Enforces the intended directory access authorizations that path traversal would otherwise bypass.
Requires secure baseline settings that disable directory listing on servers and file shares.
Restricts unnecessary server features such as automatic directory indexing.
Input validation directly neutralizes special path elements before pathname construction occurs.
Controls information flows so directory contents are not disclosed to unauthorized recipients.
Least privilege reduces the impact of any unauthorized file access obtained via traversal.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened baselines and config management directly disable directory listing by default.
Lifecycle management includes applying secure configurations that would prevent directory exposure.
Vulnerability scanning can discover exposed directories so they can be remediated.
Least-privilege access rules can restrict who sees directory contents but do not address the listing feature itself.
Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Information access restriction directly prevents directory listings by enforcing need-to-know access controls on web resources.
Security testing in development catches path traversal via static/dynamic analysis.
Network security measures such as disabling directory indexing on web servers reduce exposure of directory contents.
Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.
Application security requirements include rules for safe file handling and canonicalization.
Secure architecture principles require least-privilege file access and directory isolation.