All vulnerabilities

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
Weakness
CWE-1325Allocation without limits (CWE-770)
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.

From the GitHub Advisory Database, CC BY 4.0. Shortened; the full text is there.

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…

Workarounds as given by the GitHub Advisory Database, CC BY 4.0.

Affected software

SoftwareAffected versions
guzzlehttp/guzzlePackagist · osv:Packagist:guzzlehttp/guzzle
  • Every version before 7.15.1

About guzzlehttp/guzzle

Monthly downloads (Packagist)
35,230,404Packagist, 16 Nov 2026
Total downloads (Packagist)
1,162,991,182Packagist, 16 Nov 2026

References