Skip to main content
No exploitation reportedFix available

CVE-2022-29248

No exploitation reported by the sources we read.

  • Published2022-05-25
  • Fixed in9.3.14 · 9.2.20
  • WeaknessCWE-200 · CWE-565

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2022-05-2518:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-29248?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-29248?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Drupal
BranchAffectedFixed in
9.3≥ 9.3.0, < 9.3.149.3.14
9.2≥ 9.2.0, < 9.2.209.2.20
9.2≥ 8.0.0, < 9.2.209.2.20
Guzzlephp guzzle
BranchAffectedFixed in
7.x≥ 7.0.0, < 7.4.37.4.3
6.5< 6.5.66.5.6
Debian debian linux
BranchAffectedFixed in
11.0= 11.0no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Drupal to 9.3.14 · 9.2.20

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2025-04-23
  • OpenCVESSVC decisionnone—
  • CNACVSS 3.18read 2026-10-23
  • NVDCVSS 3.18.1read 2026-10-23
  • NVDCVSS 2.05.8read 2026-10-23
  • CNAweakness (CWE)CWE-200read 2026-10-23
  • NVDweakness (CWE)CWE-565read 2026-10-23
  • FIRST EPSSEPSS score1.4 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Published
2022-05-25
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-29248?

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.

Is CVE-2022-29248 actively exploited?

Active exploitation of CVE-2022-29248 has not been confirmed. Its EPSS score was 1.4% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-29248?

CVE-2022-29248 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.

Running guzzlehttp/guzzle? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month