# CVE-2022-32206: Denial of service in https://github.com/curl/curl

> A malicious server can cause curl to exhaust memory via unbounded decompression chains, leading to denial of service.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Jul 2022
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2022-32206, AZL-10102, CLEANSTART-2026-TI45822, CURL-CVE-2022-32206, DEBIAN-CVE-2022-32206, GHSA-pphv-gw4r-gww8, JLSEC-2026-393, UBUNTU-CVE-2022-32206

## What is CVE-2022-32206?

CVE-2022-32206 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms. The number of acceptable "links" in this "decompression chain" was unbounded, allowing a malicious server to insert a virtually unlimited number of compression steps.The use of such a decompression chain could result in a "malloc bomb", makingcurl end up spending enormous amounts of allocated heap memory, or trying toand returning out of memory errors.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 19 products.


Products: Debian Debian Linux, Fedoraproject Fedora, Haxx Curl, Netapp Bootstrap Os, Netapp Clustered Data Ontap, Netapp Element Software, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Netapp Hci Management Node, Netapp Solidfire, Siemens Scalance Sc622-2c Firmware, Siemens Scalance Sc626-2c Firmware, Siemens Scalance Sc632-2c Firmware, Siemens Scalance Sc636-2c Firmware, Siemens Scalance Sc642-2c Firmware, Siemens Scalance Sc646-2c Firmware, Splunk Universal Forwarder.

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

Upgrade to a fixed version.

## Is CVE-2022-32206 being exploited?

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

## 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-32206 and fix it if it is affected.

What it is: CVE-2022-32206 is a medium-severity denial of service vulnerability in Debian Debian Linux, published on 7 Jul 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32206 exists.

Affected product: Debian Debian Linux. 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-2022-32206/ (Markdown: https://insights.sbomify.com/CVE-2022-32206/index.md)
```

## Sources

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

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