# CVE-2021-22946: Security feature bypass in https://github.com/curl/curl

> Attackers can bypass TLS enforcement in curl for IMAP, POP3, or FTP, causing sensitive data to be transmitted in clear text.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 29 Sep 2021
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2021-22946, AZL-6365, CLEANSTART-2026-HL19733, CURL-CVE-2021-22946, DEBIAN-CVE-2021-22946, ECHO-e654-6dd5-09ec, GHSA-3cmq-42w4-c529, JLSEC-2026-1339, UBUNTU-CVE-2021-22946

## What is CVE-2021-22946?

CVE-2021-22946 is a high-severity vulnerability in Apple Macos, published on 29 Sep 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or `CURLUSESSL_ALL` withlibcurl). This requirement could be bypassed if the server would return a properly crafted but perfectly legitimate response.This flaw would then make curl silently continue its operations **withoutTLS** contrary to the instructions and expectations, exposing possibly sensitive data in clear text over the network.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information), CWE-325 (Missing Cryptographic Step)

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

It affects 29 products.


Products: Apple Macos, Debian Debian Linux, Fedoraproject Fedora, Haxx Curl, Netapp Cloud Backup, Netapp Clustered Data Ontap, Netapp H300e Firmware, Netapp H300s Firmware, Netapp H410s Firmware, Netapp H500e Firmware, Netapp H500s Firmware, Netapp H700e Firmware, Netapp H700s Firmware, Netapp Oncommand Insight, Netapp Oncommand Workflow Automation, Netapp Snapcenter, Netapp Solidfire Baseboard Management Controller Firmware, Oracle Commerce Guided Search, Oracle Communications Cloud Native Core Binding Support Function, Oracle Communications Cloud Native Core Console and 9 more.

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

Upgrade to a fixed version.

## Is CVE-2021-22946 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-22946 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-2021-22946 and fix it if it is affected.

What it is: CVE-2021-22946 is a high-severity vulnerability in Apple Macos, published on 29 Sep 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-22946 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-2021-22946/ (Markdown: https://insights.sbomify.com/CVE-2021-22946/index.md)
```

## Sources

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

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