All vulnerabilities

Packagist

CVE-2026-67354

Guzzle: URI fragments disclosed in redirect Referer headers

Severity
Medium 5.9
Published
20 Jul 2026
Last changed
10 Sept 2026
Added to UpHeron
23 Oct 2026
Fixed in
7.15.1
Exploit chance
0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Information exposure through sent data (CWE-201)CWE-212
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Also known as
GHSA-h95v-h523-3mw8
Sources
OSV.dev and GitHub

Description

When the optional referer redirect setting is enabled, affected versions of RedirectMiddleware can copy the fragment from the referring request URI into a generated Referer header. A URI fragment is the part after #. It is handled locally by the client and is not part of the HTTP request target, so the server handling the original request does not receive it. A generated Referer tells the redirect destination which URI led to the request. Guzzle correctly removes user information from that value, but retains the fragment when it follows a redirect to the same scheme, such as HTTPS to HTTPS. For example, an initial URI ending in #secret is sent without the fragment, but the redirect destination can receive a Referer ending in #secret. This behavior affects both the cURL and stream handlers.

An attacker who controls the redirect destination can read the fragment from the incoming header, including through request logs or application code.

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

Workarounds

If you cannot upgrade immediately, leave automatic Referer generation disabled. It is off by default. If redirect options are configured explicitly, ensure that referer is false:

Alternatively, disable automatic redirects and follow trusted destinations manually, or remove the fragment from the request URI before sending a request that may redirect. Do not rely on the fact that fragments are absent from the initial HTTP request target, because the affected middleware can reintroduce them in the generated header.

Workarounds as given by the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
guzzlehttp/guzzlePackagist · osv:Packagist:guzzlehttp/guzzle
  • Every version before 7.15.1

About guzzlehttp/guzzle

Monthly downloads (Packagist)
35,230,404Packagist, 16 Nov 2026
Total downloads (Packagist)
1,162,991,182Packagist, 16 Nov 2026

References