Guzzle up to 7.15.1/8.0.0 Cookie Domain Matching SetCookie::matchesDomain config

Summaryinfo

A vulnerability classified as critical was found in Guzzle up to 7.15.1/8.0.0. Affected by this issue is the function SetCookie::matchesDomain of the component Cookie Domain Matching. Executing a manipulation can lead to config. This vulnerability is tracked as CVE-2026-69245. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in Guzzle up to 7.15.1/8.0.0 and classified as critical. This vulnerability affects the function SetCookie::matchesDomain of the component Cookie Domain Matching. The manipulation with an unknown input leads to a config vulnerability. The CWE definition for the vulnerability is CWE-16. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-69245 since 08/03/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.004.

Upgrading to version 7.15.2 or 8.0.1 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Name

• Guzzle

Version

• 7.15.0
• 7.15.1
• 8.0

Website

• Product: https://github.com/guzzle/guzzle/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion