Packagist
CVE-2026-67355
Guzzle: Host-only cookie scope is not preserved
- Severity
- Medium 5.9
- Published
- 20 Jul 2026
- Last changed
- 10 Sept 2026
- Added to UpHeron
- 23 Oct 2026
- Fixed in
- 7.15.1
- Exploit chance
- 0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Only under certain conditions · No login needed · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N- Also known as
- GHSA-wm3w-8rrp-j577
- Sources
- OSV.dev and GitHub
Description
In affected versions, CookieJar does not preserve whether a response cookie was set without a Domain attribute or with an empty one. A cookie without Domain is host-only and must be returned only to the exact host that set it. Under current cookie processing rules, an empty Domain value is also host-only. Guzzle instead stores the request host in the cookie's Domain field and later applies ordinary domain matching, as though the server had supplied a valid domain. For example, a host-only sid=secret cookie set by example.com can subsequently be sent to child.example.com. FileCookieJar and SessionCookieJar also persist the request host without recording the host-only state, so reloading a jar preserves the widened scope.
An attacker who controls or can observe a child host can therefore receive cookies that were intended only for its parent host. Depending on the cookie, this can disclose session identifiers, authorization tokens, or other sensitive state.
Workarounds
If you cannot upgrade immediately, do not reuse one CookieJar instance across parent and child hosts with different trust levels. Use a separate cookie jar for each host or trust boundary, disable cookie handling for requests to less-trusted hosts, or avoid making those requests through a client configured with a shared jar. In particular, avoid new Client(['cookies' => true]) for a client that may contact both a trusted parent host and less-trusted subdomains, because that option creates one jar for the whole client.
Affected software
| Software | Affected versions |
|---|---|
guzzlehttp/guzzlePackagist · osv:Packagist:guzzlehttp/guzzle |
|
About guzzlehttp/guzzle
- Monthly downloads (Packagist)
- 35,230,404Packagist, 16 Nov 2026
- Total downloads (Packagist)
- 1,162,991,182Packagist, 16 Nov 2026
Vulnerabilities in guzzlehttp/guzzle
- In our list
- 9
- Published in the last 12 months
- 9
- Critical, last 12 months
- 0
- High, last 12 months
- 1
- Known exploited
- 0
- CVE-2026-69246Guzzle: Noncanonical host can bypass host-based checksHigh 7.2 3 Aug 2026
- CVE-2026-69245Guzzle: Noncanonical cookie domain keeps subdomain scopeMedium 6.5 3 Aug 2026
- CVE-2026-67354Guzzle: URI fragments disclosed in redirect Referer headersMedium 5.9 20 Jul 2026
- CVE-2026-67353Guzzle: Unbounded response cookies risk denial of serviceMedium 5.3 20 Jul 2026
- CVE-2026-59883Guzzle: Cookie Disclosure and Injection via IP-Address DomainsMedium 4.7 20 Jul 2026
- CVE-2026-67339Guzzle: Proxy-Authorization headers can be sent to origin serversMedium 5.3 20 Jul 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67355
- GitHub Advisory Database https://github.com/advisories/GHSA-wm3w-8rrp-j577