ManageIQ / ManageIQ/kubeclient

CVE-2026-33637 (Low) detected in faraday-2.14.0.gem

Open Beginner friendly
#712 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-33637 - Low Severity Vulnerability

Vulnerable Library - faraday-2.14.0.gem

Library home page: https://rubygems.org/gems/faraday-2.14.0.gem

Sample Path to Dependency File: /Gemfile.lock

Path to vulnerable library: /vendor/cache/faraday-2.14.0.gem

Dependency Hierarchy:

  • googleauth-1.15.1.gem (Root Library)
    • faraday-2.14.0.gem (Vulnerable Library)

Found in base branch: master

Vulnerability Details

Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters. Versions 2.0.0 through 2.14.1 still allow protocol-relative host override when the request target is passed as a URI object (rather than a String) to Faraday::Connection#build_exclusive_url. This bypasses the February 2026 fix for GHSA-33mh-2634-fwr2 and enables off-host request forgery: a request built from a fixed-base Faraday::Connection can be redirected to an attacker-controlled host, forwarding connection-scoped values such as Authorization headers and default query parameters. This issue has been fixed in version 2.14.3.

Publish Date: 2026-05-19

URL: CVE-2026-33637

CVSS 3 Score Details (0.0)

Base Score Metrics:

  • Exploitability Metrics:
    • Attack Vector: Network
    • Attack Complexity: Low
    • Privileges Required: None
    • User Interaction: None
    • Scope: Unchanged
  • Impact Metrics:
    • Confidentiality Impact: None
    • 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-5rv5-xj5j-3484

Release Date: 2026-05-18

Fix Resolution: faraday - 2.14.2


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 the vendored dependency at vendor/cache/faraday-2.14.0.gem, following the googleauth dependency path described in the issue. Update Faraday to the issue's stated fixed release, reconcile the differing suggested versions, and verify the dependency files and relevant project checks pass.

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
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.