CVE-2022-29248 | Cross-domain cookie leakage in Guzzle

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.

Published: 2022-05-25 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-29248 is rated Moderate Risk (56.6/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.64%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-29248

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-01 0.45% 0.64% +0.18%
2 2025-10-07 0.61% 0.45% -0.16%
3 2025-10-06 — 0.61% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-29248

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.0 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 5.8 [email protected]
8.1 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]
5.8 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 4.9 [email protected]

Weakness enumeration for CVE-2022-29248

GitHub Security Advisory for CVE-2022-29248

GHSA-cwmx-hcrq-mhc3 · Severity: high · Ecosystem: composer — Cross-domain cookie leakage in Guzzle

OS Trackers for CVE-2022-29248

vendor priority summary link
debian not yet assigned CVE-2022-29248 not yet assigned priority: Debian including 2 source packages (guzzle, mediawiki), 9 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 9. https://security-tracker.debian.org/tracker/CVE-2022-29248
ubuntu medium CVE-2022-29248 medium priority: Ubuntu including 2 source packages (guzzle, php-guzzle), 9 status rows across 8 suites (kinetic, lunar, mantic, noble, oracular, plucky, questing, upstream): ignored 5, needs-triage 4. https://ubuntu.com/security/CVE-2022-29248

Affected software / configurations for CVE-2022-29248

Vendor Product Version Raw CPE
guzzlephp guzzle < 6.5.6 cpe:2.3:a:guzzlephp:guzzle:*:*:*:*:*:*:*:*
guzzlephp guzzle >= 7.0.0, < 7.4.3 cpe:2.3:a:guzzlephp:guzzle:*:*:*:*:*:*:*:*
drupal drupal >= 9.2.0, < 9.2.20 cpe:2.3:a:drupal:drupal:*:*:*:*:*:*:*:*
drupal drupal >= 9.3.0, < 9.3.14 cpe:2.3:a:drupal:drupal:*:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2022-29248

cvelogic Threat Intelligence