CVE-2022-29248

Cross-domain cookie leakage in Guzzle

HIGH
8.1
CVSS Score
Published: May 25, 2022 at 12:00 AM UTC
Updated: June 17, 2026 at 04:39 AM UTC
4 products affected across 4 vendorsDebian LinuxDrupalGuzzle

Using guzzle by guzzle?

Get instant alerts when new vulnerabilities affect guzzle - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

Guzzle is a PHP HTTP client. Guzzle prior to versions 6.5.6 and 7.4.3 contains a vulnerability with the cookie middleware. The vulnerability is that it is not checked if the cookie domain equals the domain of the server which sets the cookie via the Set-Cookie header, allowing a malicious server to set cookies for unrelated domains. The cookie middleware is disabled by default, so most library consumers will not be affected by this issue. Only those who manually add the cookie middleware to the handler stack or construct the client with ['cookies' => true] are affected. Moreover, those who do not use the same Guzzle client to call multiple domains and have disabled redirect forwarding are not affected by this vulnerability. Guzzle versions 6.5.6 and 7.4.3 contain a patch for this issue. As a workaround, turn off the cookie middleware.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

9.2.0 ≤ v < 9.2.209.3.0 ≤ v < 9.3.14
Affected range stops below 9.2.20, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.3.14, so it looks safe — our inference, not a vendor statement
v < 6.5.67.0.0 ≤ v < 7.4.3
Affected range stops below 6.5.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement
v < 6.5.6v < 7.4.3
Affected range stops below 6.5.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.4.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200CWE-565

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card