Is CVE-2026-69245 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-69245 being exploited in the wild.

How severe is CVE-2026-69245?

Medium severity, with a CVSS score of 6.5, published 3 August 2026.

Which products and versions are affected?

guzzlehttp/guzzle (Packagist) ECOSYSTEM:introduced=0,fixed=7.15.2.

Is there a fix for CVE-2026-69245?

Yes. guzzlehttp/guzzle (Packagist): upgrade to 7.15.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-69245 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-69245?

Check whether you run guzzlehttp/guzzle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-69245: Guzzle incorrect cookie domain matching for noncanonical IP addresses

CVE-2026-69245 · Severity: medium · CVSS 6.5 · Published 2026-08-03

Guzzle is a popular PHP library used by applications to make web requests. A flaw in how it handles cookies allows sensitive session information to be sent to unintended websites if the application uses non-standard IP address formats (like hexadecimal or percent-encoded addresses). This could lead to account takeover or session fixation if an attacker controls a host within the same private or container network.

Technologies: guzzlehttp/guzzle (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-69245 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69245 being exploited in the wild.
How severe is CVE-2026-69245?: Medium severity, with a CVSS score of 6.5, published 3 August 2026.
Which products and versions are affected?: guzzlehttp/guzzle (Packagist) ECOSYSTEM:introduced=0,fixed=7.15.2.
Is there a fix for CVE-2026-69245?: Yes. guzzlehttp/guzzle (Packagist): upgrade to 7.15.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69245 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-69245?: Check whether you run guzzlehttp/guzzle (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

guzzlehttp/guzzle (Packagist): upgrade to 7.15.2 or later
```
composer require guzzlehttp/guzzle:^7.15.2
```

Technical details

The `SetCookie::matchesDomain()` function fails to recognize noncanonical IP address representations (such as hexadecimal `0x7f000001` or percent-encoded `127.0.0.%31`) as IP literals. Because Guzzle treats these as registered domain names rather than fixed IP addresses, it applies suffix-based subdomain matching rules. An attacker controlling a host that ends in one of these strings (e.g., `evil.0x7f000001`) can receive cookies intended for the IP address or set cookies that the client will replay to the IP address. This bypasses the security boundary intended for IP-based origins. The issue is fixed in versions 7.15.2 and 8.0.1 by enforcing exact matches for domains containing percent signs or hexadecimal/octal parts.

Affected products

GuzzleHttp guzzle < 7.15.2, 8.0.0

Identifiers

CVE-2026-69245
GHSA-f7vp-7xgx-4w4r

Timeline

2026-07-26: disclosed
2026-08-03: advisory: GitHub Advisory published
2026-08-03: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.