Advisory record · GHSA-cwmx-hcrq-mhc3

Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. [Guzzle has released a security update](https://github.com/guzzle/guzzle/security/advisorie...

CVSS 8.0 HighEPSS 0.014 · 72nd percentile

Published by the maintainers · not yet reviewed by GitHub. The guzzle/guzzle maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the guzzle/guzzle maintainers at 25 May 2022, 19:39 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
drupal/corePackagist>=8.0.0, <9.2.20 || >=9.3.0, <9.3.149.2.20, 9.3.14
Identifiers
GHSA-cwmx-hcrq-mhc3 · BIT-drupal-2022-29248 · CVE-2022-29248 · DRUPAL-CORE-2022-010 · PKSA-6d8m-6kgw-18zr
Weakness (CWE)
CWE-200
Published
25 May 2022
Updated
19 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Drupal core (Packagist drupal/core) versions from 8.0.0 before 9.2.20 and from 9.3.0 before 9.3.14 are listed as affected, with fixed versions 9.2.20 and 9.3.14. The source says the upstream Guzzle HTTP library vulnerability does not affect Drupal core itself but may affect contributed or custom modules that use Guzzle for outgoing requests, and it gives few details of the attack. Sites should upgrade drupal/core to 9.2.20 or 9.3.14 as listed, and review contributed or custom code that uses Guzzle.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.0 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.014, the 72nd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 25 May 2022, 13:25 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 13:55 UTC First seen by agentprime
  3. 31 Oct 2026, 13:55 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.