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

> A malicious server can cause a denial of service in curl by sending excessive Set-Cookie headers, leading to request size errors.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **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-32205, AZL-10101, CLEANSTART-2026-IQ39304, CURL-CVE-2022-32205, DEBIAN-CVE-2022-32205, GHSA-9hhr-r3j8-h675, JLSEC-2026-392, UBUNTU-CVE-2022-32205

## What is CVE-2022-32205?

CVE-2022-32205 is a medium-severity denial of service vulnerability in Apple Macos, 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

A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them. A sufficiently large amount of (big) cookies make subsequent HTTP requests to this, or other servers to which the cookies match, create requests that become larger than the threshold that curl uses internally to avoid sending crazy large requests (1048576 bytes) and instead returns an error.This denial state might remain for as long as the same cookies are kept, match and haven't expired. Due to cookie matching rules, a server on `foo.example.com` can set cookies that also would match for `bar.example.com`, making it it possible for a "sister server" to effectively cause a denial of service for a sibling site on the same second level domain using this method.

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

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

It affects 19 products.


Products: Apple Macos, Debian Debian Linux, Fedoraproject Fedora, Haxx Curl, 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-32205?

Upgrade to a fixed version.

## Is CVE-2022-32205 being exploited?

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

## Other vulnerabilities in Apple Macos

- [CVE-2026-65400](https://insights.sbomify.com/CVE-2026-65400/): Apple macOS Improper Authentication (critical 9.8, exploited in the wild)
- [CVE-2024-44146](https://insights.sbomify.com/CVE-2024-44146/): Security feature bypass in macOS (critical 10.0)
- [CVE-2024-44148](https://insights.sbomify.com/CVE-2024-44148/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-38586](https://insights.sbomify.com/CVE-2023-38586/): Security feature bypass in macOS (critical 10.0)
- [CVE-2023-40455](https://insights.sbomify.com/CVE-2023-40455/): Security feature bypass in macOS (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32205 is a medium-severity denial of service vulnerability in Apple Macos, 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-32205 exists.

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

## Sources

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

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