Packagist
CVE-2026-69246
Guzzle: Noncanonical host can bypass host-based checks
- Severity
- High 7.2
- Published
- 3 Aug 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 23 Oct 2026
- Fixed in
- 7.15.2, 8.0.1
- Exploit chance
- 0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N- Also known as
- GHSA-v5mv-p594-2x33
- Sources
- OSV.dev and GitHub
Description
In affected versions, Guzzle gives a transport the request URI as text and supplies the Host header separately. The cURL handlers set CURLOPT_URL to the URI exactly as written and push that Host into CURLOPT_HTTPHEADER; StreamHandler does the same through fopen(). libcurl then parses the authority itself, percent-decoding it and, on an IDN-capable build, applying IDNA mapping, and uses the result to resolve, connect, name the TLS peer and address a proxy CONNECT, while the supplied Host suppresses the aligned one it would have generated. In http://127.0.0.%31/ the URI host is one filter_var() rejects as an IP literal, yet libcurl decodes it to 127.0.0.1 and reaches loopback with no DNS lookup while the server receives Host: 127.0.0.%31.
An attacker who influences a fetched URI can therefore reach a host the application's checks excluded and read whatever it exposes of the response.
Workarounds
If you cannot upgrade, constrain the host yourself before handing a URI to Guzzle, and constrain any explicit Host header separately, on every redirect hop. The URI rule assumes $uri is a validated GuzzleHttp\Psr7\Uri, so re-parse a third-party UriInterface with new Uri((string) $uri) first.
It differs from the patch in both directions: it refuses example.com., which the patch accepts, and it does not canonicalize 127.1 or 0x7f000001. Reparsing the URI separates a valid port from the host and rejects malformed bracket forms, so the snippet checks the host component alone.
Affected software
| Software | Affected versions |
|---|---|
guzzlehttp/guzzlePackagist · osv:Packagist:guzzlehttp/guzzle |
|
About guzzlehttp/guzzle
- Monthly downloads (Packagist)
- 35,230,404Packagist, 16 Nov 2026
- Total downloads (Packagist)
- 1,162,991,182Packagist, 16 Nov 2026
Vulnerabilities in guzzlehttp/guzzle
- In our list
- 9
- Published in the last 12 months
- 9
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-69245Guzzle: Noncanonical cookie domain keeps subdomain scopeMedium 6.5 3 Aug 2026
- CVE-2026-67354Guzzle: URI fragments disclosed in redirect Referer headersMedium 5.9 20 Jul 2026
- CVE-2026-67355Guzzle: Host-only cookie scope is not preservedMedium 5.9 20 Jul 2026
- CVE-2026-67353Guzzle: Unbounded response cookies risk denial of serviceMedium 5.3 20 Jul 2026
- CVE-2026-59883Guzzle: Cookie Disclosure and Injection via IP-Address DomainsMedium 4.7 20 Jul 2026
- CVE-2026-67339Guzzle: Proxy-Authorization headers can be sent to origin serversMedium 5.3 20 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-69246
- GitHub Advisory Database https://github.com/advisories/GHSA-v5mv-p594-2x33