ManageIQ / ManageIQ/kubeclient

CVE-2026-25500 (Medium) detected in rack-3.2.3.gem

Open
#686 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

CVE-2026-25500 - Medium Severity Vulnerability

Vulnerable Library - rack-3.2.3.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.3.gem

Sample Path to Dependency File: /Gemfile.lock

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

Dependency Hierarchy:

  • openid_connect-1.4.2.gem (Root Library)
    • rack-oauth2-1.21.3.gem
      • rack-3.2.3.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" generates an HTML directory index where each file entry is rendered as a clickable link. If a file exists on disk whose basename starts with the "javascript:" scheme (e.g. "javascript:alert(1)"), the generated index contains an anchor whose "href" is exactly "javascript:alert(1)". Clicking the entry executes JavaScript in the browser (demonstrated with "alert(1)"). Versions 2.2.22, 3.1.20, and 3.2.5 fix the issue.

Publish Date: 2026-02-18

URL: CVE-2026-25500

CVSS 3 Score Details (5.4)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: Low
    • User Interaction: Required
    • Scope: Changed
  • Impact Metrics:
    • Confidentiality Impact: Low
    • Integrity Impact: Low
    • 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 - v2.2.22,https://github.com/rack/rack.git - v3.2.5,https://github.com/rack/rack.git - v3.1.20


Step up your Open Source Security Game with Mend here

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.2.3.gem to trace how Rack is pinned through the dependency hierarchy. Update the dependency to a fixed Rack release listed in the issue, then run the repository's test suite; done means the vulnerable Rack version is no longer present.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend, security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.