CVE-2026-54171

Excon: redact additional sensitive/risky headers when following redirects

Published Jul 17, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
Description
Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial request includes header information that is not intended for the new target. This issue is fixed in version 1.5.0.

Analysis

AI-generated

Technical impact

Excon, a lightweight Ruby HTTP client, contained a bug in its RedirectFollower middleware that did not remove sensitive headers when following redirects. The flaw allowed any header present in the original request—such as authentication tokens, session identifiers, or other privileged data—to be forwarded to the redirect target, exposing confidential information that was not intended for that domain. This is an information‑exposure vulnerability classified as CWE‑201.

Affected Systems

Ruby applications that employ the Excon gem before version 1.5.0 are vulnerable. Any software that imports Excon and performs HTTP requests with automatic redirect following enabled, without customizing a list of headers to strip, can inadvertently leak those headers to the redirect destination. This includes web applications, API clients, and scripts that rely on Excon's default redirect handling.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity, while the EPSS score of less than 1% suggests a low probability of exploitation at present. The vulnerability is not listed in the CISA KEV catalog. Exploitation generally requires an attacker to influence or control the redirect target so that the application forwards its request headers to an attacker‑controlled domain, thereby exfiltrating sensitive data without user awareness. The primary risk is to confidentiality; availability is not affected.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Excon gem to version 1.5.0 or later to apply the official fix
  • If upgrading is not immediately possible, configure a custom middleware or use Excon's options to explicitly strip sensitive headers before following a redirect
  • Disable automatic redirect handling or restrict redirects to trusted domains only

Generated by OpenCVE AI on July 30, 2026 at 23:32 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-48rx-c7pg-q66r Excon does not redact additional sensitive/risky headers when following redirects
History
Type Values Removed Values Added
First Time appeared Excon
Excon excon
Vendors & Products Excon
Excon excon
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Excon is usable, fast, simple HTTP 1.1 for Ruby. Prior to 1.5.0, Excon's RedirectFollower middleware failed to strip additional sensitive headers when following redirects and did not provide a custom list of headers to strip. This could cause inadvertent leakage of sensitive data when the initial request includes header information that is not intended for the new target. This issue is fixed in version 1.5.0.
Title Excon: redact additional sensitive/risky headers when following redirects
Weaknesses CWE-201
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 20, 2026, 1:59 PM
Reserved
Jun 11, 2026, 9:46 PM
Status
Analyzed
Published
Jul 17, 2026, 8:17 PM
Modified
Jul 29, 2026, 3:20 PM