ManageIQ / ManageIQ/linux_admin

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

Open Beginner friendly
#270 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mend: dependency security vulnerability stale
Dominant language
Ruby
Stars
30
Forks
27
PR merge metrics
No merged PRs in 30d

Description

## CVE-2026-22860 - High Severity Vulnerability
Vulnerable Library - rack-3.1.16.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.1.16.gem


Path to dependency file: /Gemfile.lock


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


Dependency Hierarchy:
- manageiq-style-1.3.3.gem (Root Library)
- rubocop-rails-2.32.0.gem
- :x: **rack-3.1.16.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)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with /Gemfile.lock and /vendor/cache/rack-3.1.16.gem, then inspect the dependency path through rubocop-rails. Update the resolved Rack dependency to a fixed release listed in the issue and refresh the lockfile or cached gem as appropriate. Done means the project no longer resolves Rack 3.1.16 and uses a fixed version.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.