# CVE-2022-31090: CURLOPT_HTTPAUTH option not cleared on change of origin in Guzzle

> Attackers can steal sensitive Authorization headers when Guzzle follows cross-origin redirects using the Curl handler, exposing credentials to unintended destinations.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jun 2022
- **Updated:** 23 Apr 2025
- **Also known as:** DEBIAN-CVE-2022-31090, GHSA-25mq-v84q-4j7r, UBUNTU-CVE-2022-31090

## What is CVE-2022-31090?

CVE-2022-31090 is a high-severity vulnerability in Debian Debian Linux, published on 27 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2022-31090?

4 open source packages ship an affected version, including guzzlehttp/guzzle. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `guzzlehttp/guzzle` | Packagist | All versions | 6.5.8 |
| `guzzlehttp/guzzle` | Packagist | All versions | 6.5.8 |
| `guzzlehttp/guzzle` | Packagist | From 7.0.0 | 7.4.5 |
| `guzzlehttp/guzzle` | Packagist | From 7.0.0 | 7.4.5 |

Products: Debian Debian Linux, Guzzlephp Guzzle.

## How do I fix CVE-2022-31090?

Upgrade guzzlehttp/guzzle to a fixed version for your release line: 6.5.8 or 7.4.5.

## Is CVE-2022-31090 being exploited?

There is no known exploitation of CVE-2022-31090 in the wild and no public exploit code.

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-31090 and fix it if it is affected.

What it is: CVE-2022-31090 is a high-severity vulnerability in Debian Debian Linux, published on 27 Jun 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-31090 in the wild and no public exploit code.

Affected packages and fixed versions:
- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 6.5.8
- guzzlehttp/guzzle (Packagist): affected all versions; fixed in 6.5.8
- guzzlehttp/guzzle (Packagist): affected from 7.0.0; fixed in 7.4.5
- guzzlehttp/guzzle (Packagist): affected from 7.0.0; fixed in 7.4.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-31090/ (Markdown: https://insights.sbomify.com/CVE-2022-31090/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-31090
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-31090
- OSV: https://osv.dev/vulnerability/CVE-2022-31090

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-31090/
Summaries are generated and may contain mistakes; the official description above is the record.