CVE-2026-22860 (High) detected in rack-3.2.4.gem

## CVE-2026-22860 - High Severity Vulnerability
Vulnerable Library - rack-3.2.4.gem

Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.

Library home page: https://rubygems.org/gems/rack-3.2.4.gem

Path to dependency file: /Gemfile.lock

Path to vulnerable library: /vendor/cache/rack-3.2.4.gem

Dependency Hierarchy:
- manageiq-style-1.5.9.gem (Root Library)
- :x: **rack-3.2.4.gem** (Vulnerable Library)

Found in base branch: master

Vulnerability Details

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

Publish Date: 2026-02-18

URL: CVE-2026-22860

CVSS 3 Score Details (7.5)

Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-02-17

Fix Resolution: https://github.com/rack/rack.git - v3.2.5,https://github.com/rack/rack.git - v3.1.20,https://github.com/rack/rack.git - v2.2.22

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Start by inspecting /Gemfile.lock and the cached package at /vendor/cache/rack-3.2.4.gem, then review the CVE details and the dependency hierarchy. Done means the project uses a Rack release containing the fix and no longer reports rack-3.2.4.gem as vulnerable.

Written by the indexing model from the issue text.