# CVE-2021-22876: Information disclosure in https://github.com/curl/curl

> Attackers can steal credentials leaked in HTTP Referer headers when curl redirects requests, exposing sensitive user data to unauthorized servers.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2021
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2021-22876, CLEANSTART-2026-VF29502, CLSA-2021-1617285762, CLSA-2021-1634922432, CURL-CVE-2021-22876, DEBIAN-CVE-2021-22876, DLA-2664-1, GHSA-jjr6-2g8j-hmwr, JLSEC-2025-26, SUSE-SU-2021:1396-1, SUSE-SU-2021:14707-1, UBUNTU-CVE-2021-22876, USN-4903-1

## What is CVE-2021-22876?

CVE-2021-22876 is a medium-severity vulnerability in Broadcom Fabric Operating System, published on 1 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of Private Personal Information to an Unauthorized Actor" by leaking credentials in the HTTP Referer: header. libcurl does not strip off user credentials from the URL when automatically populating the Referer: HTTP request header field in outgoing HTTP requests, and therefore risks leaking sensitive data to the server that is the target of the second HTTP request.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-359 (Exposure of Private Personal Information to an Unauthorized Actor)

## Which versions are affected by CVE-2021-22876?

It affects 12 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `curl-openssl1` | SUSE:Linux Enterprise Server 11-SECURITY | All versions | 7.37.0-70.60.1 |
| `curl` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 7.60.0-11.15.1 |
| `curl` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 7.60.0-11.15.1 |
| `curl` | SUSE:Linux Enterprise Software Development Kit 12 SP5 | All versions | 7.60.0-11.15.1 |

Products: Broadcom Fabric Operating System, Debian Debian Linux, Fedoraproject Fedora, Haxx Libcurl, Netapp Hci Compute Node, Netapp Hci Management Node, Netapp Hci Storage Node, Netapp Solidfire, Oracle Communications Billing and Revenue Management, Oracle Essbase, Siemens Sinec Infrastructure Network Services, Splunk Universal Forwarder.

## How do I fix CVE-2021-22876?

Upgrade to a fixed version.

## Is CVE-2021-22876 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22876 exists.

## Other vulnerabilities in Broadcom Fabric Operating System

- [CVE-2025-1976](https://insights.sbomify.com/CVE-2025-1976/): Broadcom Brocade Fabric OS Code Injection (high 8.6, exploited in the wild)
- [CVE-2021-22555](https://insights.sbomify.com/CVE-2021-22555/): Linux Kernel Heap Out-of-Bounds Write (high 8.3, exploited in the wild)
- [CVE-2022-33186](https://insights.sbomify.com/CVE-2022-33186/): Command injection in Brocade Fabric OS (critical 9.8)
- [CVE-2021-27797](https://insights.sbomify.com/CVE-2021-27797/): Hardcoded credentials in Brocade Fabric OS (critical 9.8)
- [CVE-2020-15371](https://insights.sbomify.com/CVE-2020-15371/): Code injection in Brocade Fabric OS (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-22876 and fix it if it is affected.

What it is: CVE-2021-22876 is a medium-severity vulnerability in Broadcom Fabric Operating System, published on 1 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22876 exists.

Affected product: Broadcom Fabric Operating System. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2021-22876/ (Markdown: https://insights.sbomify.com/CVE-2021-22876/index.md)
```

## Sources

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

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