CVE-2022-31091: Change in port should be considered a change in origin in Guzzle

Severity: high (CVSS 7.7 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 1.6% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2022-06-27 · updated 2026-06-17
Weakness: CWE-200

Description

Guzzle, an extensible PHP HTTP client. `Authorization` and `Cookie` headers on requests are sensitive information. In affected versions on making a request which responds with a redirect to a URI with a different port, if we choose to follow it, we should remove the `Authorization` and `Cookie` headers from the request, before containing. Previously, we would only consider a change in host or scheme. Affected Guzzle 7 users should upgrade to Guzzle 7.4.5 as soon as possible. Affected users using any earlier series of Guzzle should upgrade to Guzzle 6.5.8 or 7.4.5. Note that a partial fix was implemented in Guzzle 7.4.2, where a change in host would trigger removal of the curl-added Authorization header, however this earlier fix did not cover change in scheme or change in port. An alternative approach would be to use your own redirect middleware, rather than ours, if you are unable to upgrade. If you do not require or expect redirects to be followed, one should simply disable redirects all together.

Affected products

Debian Linux: 11.0
guzzle: before 6.5.8; from 7.0.0 before 7.4.5 — fixed in 6.5.8, 7.4.5
Packagist Guzzlehttp/Guzzle: before 6.5.8; from 7.0.0 before 7.4.5; 4.0.0, 4.0.0-rc.1, 4.0.0-rc.2, 4.0.1, 4.0.2, 4.1.0 (+126) — fixed in 6.5.8, 7.4.5

How to fix

Upgrade to a fixed version: guzzle 6.5.8, 7.4.5; Packagist Guzzlehttp/Guzzle 6.5.8, 7.4.5. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2022-31091 or the next vulnerability affects your stack