ManageIQ / ManageIQ/dbus_api_service
CVE-2026-34763 (Medium) detected in rack-2.2.9.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 1
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
## CVE-2026-34763 - Medium Severity Vulnerability
Vulnerable Library - rack-2.2.9.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-2.2.9.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /home/wss-scanner/.gem/ruby/3.2.0/cache/rack-2.2.9.gem
Dependency Hierarchy:
- rack-test-2.1.0.gem (Root Library)
- :x: **rack-2.2.9.gem** (Vulnerable Library)
Found in base branch: master
Rack is a modular Ruby web server interface. Prior to versions 2.2.23, 3.1.21, and 3.2.6, Rack::Directory interpolates the configured root path directly into a regular expression when deriving the displayed directory path. If root contains regex metacharacters such as +, *, or ., the prefix stripping can fail and the generated directory listing may expose the full filesystem path in the HTML output. 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-34763
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Type: Upgrade version
Origin: https://github.com/advisories/GHSA-7mqq-6cf9-v2qp
Release Date: 2026-04-02
Fix Resolution: rack - 3.2.6,rack - 2.2.23,rack - 3.1.21
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting /Gemfile.lock and the dependency hierarchy showing rack-test-2.1.0.gem pulling in rack-2.2.9.gem. Update the Rack dependency to a listed patched version, then run the project's existing checks. Done means the lockfile resolves Rack to 2.2.23, 3.1.21, or 3.2.6 without breaking the dependency.
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
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100