CVE-2026-69246
HighCVSS 7.2Exploitation Probability (EPSS)
Low risk12th percentile - higher than 12% of all known CVEs
Summary
Guzzle, an extensible PHP HTTP client, prior to versions 7.15.2 and 8.0.1, has a vulnerability due to discrepancy between Guzzle's URI parsing and libcurl's. An attacker influencing the request URI can bypass application checks and access hosts that should be blocked. Fixed in versions 7.15.2 and 8.0.1.
Risk Assessment
An attacker can bypass security mechanisms like no_proxy and access internal network resources, potentially leading to data leakage.
Recommendation
Update Guzzle to version 7.15.2 or 8.0.1 (depending on the branch used).
Other vulnerabilities in Guzzle
See all- CVE-2026-69245Medium
Guzzle prior to versions 7.15.2 and 8.0.1 contains a vulnerability in the SetCookie::matchesDomain() method that incorrectly recognizes domains in hexadecimal or mixed-base forms (e.g., 0x7f000001) as IP addresses. Cookies set for such domains may be sent to other hosts, leading to disclosure of session identifiers or tokens.
- CVE-2026-59883Medium
In the Guzzle PHP HTTP client library prior to version 7.12.3, a vulnerability was found in the CookieJar class. The SetCookie::matchesDomain() method incorrectly handled IP addresses (e.g., 192.168.0.1, [::1]) and bare numeric values as domains by applying ordinary suffix matching, allowing cross-host cookie disclosure, cookie injection, or session fixation.
Original NVD description (English source)
Guzzle is an extensible PHP HTTP client. Prior to 7.15.2 and 8.0.1, 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 libcurl would have generated. For a URI host written as 127.0.0.%31, filter_var() rejects the host 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 the host exposes of the response. The same divergence moves Guzzle's own decisions onto a spelling the transport does not use: no_proxy selects proxy routing from the literal host, and RedirectMiddleware decides from it whether to strip Authorization and Cookie. Exploitation requires the application to build a request URI from untrusted input and to make a host decision before handing it to Guzzle. This issue is fixed in versions 7.15.2 and 8.0.1.