DRUPAL-CORE-2022-011 in drupal/core
Published 10 Jun 2022 · Updated 19 Sept 2026
Affected package
- Affected
- >=8.0.0 <9.2.21 · >=9.3.0 <9.3.16
- Fixed in
- 9.2.21, 9.3.16
composer require drupal/core:^9.3.16Details
*Updated 22:00 UTC 2022-06-10: Added steps to update without drupal/core-recommended.*
Drupal uses the third-party Guzzle library for handling HTTP requests and responses to external services. Guzzle has released two security advisories:
- Failure to strip the Cookie header on change in host or HTTP downgrade
- Fix failure to strip Authorization header on HTTP downgrade
These do not affect Drupal core, but may affect some contributed projects or custom code on Drupal sites.
We are issuing this security advisory outside our regular Drupal security release window schedule since Guzzle has already published information about the vulnerabilities, and vulnerabilities might exist in contributed modules or custom modules that use Guzzle for outgoing requests. Guzzle has rated these vulnerabilities as high-risk.
This advisory is not covered by Drupal Steward.
Is DRUPAL-CORE-2022-011 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected drupal/core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.