CVE-2026-67354

guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer

Published Aug 1, 2026 CVSS 4.0 · 8.2 High EPSS < 1% KEV · Not listed
Description
guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value.

Analysis

AI-generated

Technical impact

The vulnerability is an information disclosure flaw located in the RedirectMiddleware of guzzlehttp/guzzle. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header during a same‑scheme redirect. An attacker who can control the redirect target can read the fragment from the incoming Referer header, potentially leaking one‑time login secrets, access tokens, state values, or other confidential client data. The flaw is defined as CWE‑201, Information Exposure Through Vulnerable Design, and a flaw in the handling of sensitive data.

Affected Systems

The affected product is the Guzzle HTTP client (guzzlehttp/guzzle) distributed by guzzle:guzzle. Versions prior to 7.15.1 are vulnerable; version 7.15.1 and later incorporate a fix that strips the fragment before generating the Referer header.

Risk and Exploitability

The vulnerability has a CVSS score of 8.2, indicating high severity. EPSS information is not available and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is a network context in which a client is redirected to an attacker‑controlled URL; the attacker must have the ability to craft or influence the redirect. Once the redirect occurs, the client’s Referer header will expose the sensitive URI fragment to the malicious destination, constituting a significant data leakage risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Guzzle library to version 7.15.1 or later, which removes the URI fragment from the Referer header when setting allow_redirects.referer.
  • Disable the allow_redirects.referer configuration option or ensure it remains at its default disabled state to prevent the header from being populated.
  • If an immediate patch is unavailable, restrict redirect targets to known, trusted domains and monitor outbound requests for unwanted Referer headers containing fragments.

Generated by OpenCVE AI on August 2, 2026 at 02:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-h95v-h523-3mw8 Guzzle: URI fragments disclosed in redirect Referer headers
History
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 guzzlehttp/guzzle versions before 7.15.1 contain an information disclosure vulnerability in RedirectMiddleware. When the optional allow_redirects.referer setting is enabled, the middleware copies the URI fragment (the portion after '#') from the referring request into the generated Referer header when following a same-scheme redirect (e.g., HTTPS to HTTPS). An attacker who controls the redirect destination can read this fragment from the incoming Referer header, potentially disclosing one-time login secrets, access tokens, state values, or other sensitive client data to a server never meant to receive it. The referer setting is disabled by default. Fixed in 7.15.1, which strips the fragment before generating the Referer value.
Title guzzlehttp/guzzle before 7.15.1 URI Fragment Disclosure via Referer
First Time appeared Guzzlephp
Guzzlephp guzzle
Weaknesses CWE-201
CPEs cpe:2.3:a:guzzlephp:guzzle:*:*:*:*:*:*:*:*
Vendors & Products Guzzlephp
Guzzlephp guzzle
References
Metrics cvssV3_1

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

cvssV4_0

{'score': 8.2, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-201

    Insertion of Sensitive Information Into Sent Data

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 8, 2026, 3:24 PM
Reserved
Jul 29, 2026, 1:36 PM
Status
Awaiting Analysis
Published
Aug 1, 2026, 1:17 PM
Modified
Oct 8, 2026, 4:17 PM