CVE-2026-34785 (High) detected in rack-3.2.3.gem

Nobody has claimed this yet.

## CVE-2026-34785 - High 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
- :x: **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.23, 3.1.21, and 3.2.6, Rack::Static determines whether a request should be served as a static file using a simple string prefix check. When configured with URL prefixes such as "/css", it matches any request path that begins with that string, including unrelated paths such as "/css-config.env" or "/css-backup.sql". As a result, files under the static root whose names merely share the configured prefix may be served unintentionally, leading to information disclosure. This issue has been patched in versions 2.2.23, 3.1.21, and 3.2.6.

Publish Date: 2026-04-02

URL: CVE-2026-34785

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

Origin: https://github.com/advisories/GHSA-h2jq-g4cq-5ppq

Release Date: 2026-04-02

Fix Resolution: rack - 3.2.6,rack - 3.1.21,rack - 2.2.23

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

Start with Gemfile.lock and the dependency path through rack-oauth2, then inspect vendor/cache/rack-3.2.3.gem to understand how dependencies are stored. Update Rack to one of the listed fixed versions, refresh the lockfile and cached gem as needed, and run the repository test suite to confirm the dependency change is safe.

Written by the indexing model from the issue text.