CVE-2026-69245
MediumCVSS 6.5Exploitation Probability (EPSS)
Low risk4th percentile - higher than 4% of all known CVEs
Summary
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.
Risk Assessment
An attacker can intercept session cookies or authentication tokens by impersonating an IP address using an alternative spelling, enabling session hijacking or application state manipulation.
Recommendation
Upgrade Guzzle to version 7.15.2 or 8.0.1, which fix this vulnerability.
Other vulnerabilities in Guzzle
See all- CVE-2026-69246High
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.
- 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, SetCookie::matchesDomain() gives every subdomain of a cookie Domain that cookie unless SetCookie::matchesDomain() recognizes the Domain as an IP literal or a numeric host, and the decision comes from the domain's own text, so two spellings a transport reads as an address keep subdomain scope. Hexadecimal and mixed-base forms such as 0x7f000001 and 0177.0.0.0x1 go unrecognized while libcurl 8.21.0 reads both as 127.0.0.1. A percent-escaped Domain keeps that scope on both branches because percent-decoding sits above numeric parsing, so 192.168.0.%31 and 127.0.0.1%2e are registered names in the URI grammar rather than address literals, and no numeric rule in any base classifies them, while libcurl decodes the host before resolving and reads them as 192.168.0.1 and 127.0.0.1. A cookie stored for Domain=0x7f000001 is placed in the Cookie header of a request to evil.0x7f000001, disclosing a session identifier or token to a host that is not that address, and a response from evil.0x7f000001 setting Domain=0x7f000001 is accepted into the jar and replayed to the address, so a server answering for the look-alike name can fix a session or set application state. Exploitation requires the application to enable cookie support, address an origin by one of these spellings, and contact a host whose name ends in that spelling. This issue is fixed in versions 7.15.2 and 8.0.1.