Guzzle: Noncanonical cookie domain keeps subdomain scope
CVE-2026-69245GHSA-f7vp-7xgx-4w4r
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (guzzlehttp/guzzle 8.0.1, 7.15.2), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist guzzlehttp/guzzle
- Affected
- < 7.15.2>= 8.0.0, < 8.0.1
- Fixed in
- 7.15.2, 8.0.1
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-f7vp-7xgx-4w4r lists affected ranges: Packagist guzzlehttp/guzzle >=0 =8.0.0 <8.0.1 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-f7vp-7xgx-4w4r lists affected ranges: Packagist guzzlehttp/guzzle >=0 =8.0.0 <8.0.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- EPSS
- CVE-2026-69245: 0.20% estimated exploitation activity in the next 30 days; percentile 9.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact SetCookie::matchesDomain() gives every subdomain of a cookie Domain that cookie unless it recognizes the Domain as an IP literal or a numeric host, and it decides that from the domain's own text, so two spellings a transport reads as an address keep subdomain scope. On 7.15, 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, so closing them completes the rule GHSA-g446-98w2-8p5w (CVE-2026-59883) set out to establish, which cited the WHATWG IPv4 parser and so already admitted a 0x part. A percent-escaped Domain keeps that scope on both branches for a different reason: 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 it resolves and reads them as 192.168.0.1 and 127.0.0.1. The escape must fall in the rightmost label…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-f7vp-7xgx-4w4r
- Revision 1 · created ·
Published from osv record GHSA-f7vp-7xgx-4w4r
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-69245 Advisory: Guzzle: Noncanonical cookie domain keeps subdomain scope IDs: CVE-2026-69245, GHSA-f7vp-7xgx-4w4r Record: https://patchnext.com/advisories/cve-2026-69245 (revision 2, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: guzzlehttp/guzzle 8.0.1, 7.15.2. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist guzzlehttp/guzzle: affected < 7.15.2; >= 8.0.0, < 8.0.1; fixed in 7.15.2, 8.0.1 ## Suggested inspection (read-only) - Packagist guzzlehttp/guzzle: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on guzzlehttp/guzzle. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-f7vp-7xgx-4w4r (OSV record GHSA-f7vp-7xgx-4w4r lists affected ranges: Packagist guzzlehttp/guzzle >=0 =8.0.0 <8.0.1 (fixed)) - Verified: https://github.com/advisories/GHSA-f7vp-7xgx-4w4r (GitHub-reviewed advisory GHSA-f7vp-7xgx-4w4r lists affected ranges: Packagist guzzlehttp/guzzle >=0 =8.0.0 <8.0.1) Commands are suggestions: review each one before running it.
Loading voting…