Packagist
CVE-2026-67353
Guzzle: Unbounded response cookies risk denial of service
- Severity
- Medium 5.3
- 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 36% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Slow it down
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L- Also known as
- GHSA-f283-ghqc-fg79
- Sources
- OSV.dev and GitHub
Description
In affected versions, Guzzle's built-in CookieJar accepts any number of Set-Cookie header fields from one response, with no limit on the size of each field. When a later request matches the stored cookies, Guzzle places every match into one generated Cookie header without limiting the number of cookies or the total header length.
A malicious or compromised server can therefore return many large cookies, causing Guzzle to store attacker-controlled data in memory and copy it into later request headers. This can increase memory use and processing time. It can also make later requests fail when the generated header exceeds a limit in a handler, HTTP implementation, proxy, or destination server. A server on one sibling host, such as attacker.example.com, can also set parent-domain cookies that are later selected for another sibling, such as service.example.com. The denial can therefore affect a different service that uses the same jar.
Workarounds
If you cannot upgrade immediately, do not enable a shared built-in cookie jar for requests to untrusted origins. Use separate jars per host or trust boundary, disable cookie handling for untrusted requests, and discard or clear a jar after receiving an untrusted response before it is reused. Applications that must accept cookies from untrusted peers can provide a custom CookieJarInterface implementation that enforces suitable limits.
Guzzle does not use libcurl's cookie engine for cookies stored in a CookieJar. The cURL handler sends the Cookie header that Guzzle's cookie middleware has…
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-67355Guzzle: Host-only cookie scope is not preservedMedium 5.9 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-67353
- GitHub Advisory Database https://github.com/advisories/GHSA-f283-ghqc-fg79