Skip to content
Noroxi
CVE-2022-29248· NVD / CVE Program· CNA GitHub_M

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.

HighCVSS 8.1 · v3.1—No exploit Fix available
Published
May 25, 2022
Updated
Jun 17, 2026
EPSS
1.3% · 70th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

32

Monitor

Low priority for now.

CVSS
32 / 40 · 8.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
8.1
CNA · GitHub_M
8.0
0.1 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
guzzlephpguzzle
drupaldrupal
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • drupal drupal9.2.0 and later · before 9.2.20
  • drupal drupal9.3.0 and later · before 9.3.14
  • guzzlephp guzzlebefore 6.5.6
  • guzzlephp guzzle7.0.0 and later · before 7.4.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • guzzle guzzle

    • < 6.5.6, >= 7.0.0, < 7.4.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11mediawikibefore 1:1.35.8-1~deb11u11:1.35.8-1~deb11u1
Debian:12guzzlebefore 7.4.4-17.4.4-1
Debian:12mediawikibefore 1:1.35.7-11:1.35.7-1
Packagistdrupal/corefrom 8.0.0 · before 9.2.209.2.20
Packagistdrupal/corefrom 9.3.0 · before 9.3.149.3.14
Packagistguzzlehttp/guzzlefrom 7.0.0 · before 7.4.37.4.3
Packagistguzzlehttp/guzzlebefore 6.5.66.5.6

Same product

guzzlephp: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-31090CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle
    31Monitor
  • CVE-2022-31043Fix failure to strip Authorization header on HTTP downgrade in Guzzle
    31Monitor
  • CVE-2022-31042Failure to strip the Cookie header on change in host or HTTP downgrade in Guzzle
    31Monitor
  • CVE-2022-31091Change in port should be considered a change in origin in Guzzle
    30Monitor
  • CVE-2026-59883Guzzle: Cookie Disclosure and Injection via IP-Address Domains
    24Monitor
  • CVE-2026-55767Guzzle: Dot-Only Cookie Domains Match All Hosts in guzzlehttp/guzzle
    23Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:guzzle7.4.4-1 · Debian:12Package registry (OSV)
debian:mediawiki1:1.35.7-1 · Debian:12Package registry (OSV)
Packagist:drupal/core9.2.20Package registry (OSV)
Packagist:drupal/core9.3.14Package registry (OSV)
Packagist:guzzlehttp/guzzle6.5.6Package registry (OSV)
Packagist:guzzlehttp/guzzle7.4.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
None

Weakness class (CWE)

CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

The bug in code

The whole CWE-200 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records