# CVE-2020-9859: Apple Multiple Products Code Execution

> An application can execute arbitrary code with kernel privileges due to a double-free memory corruption issue in Apple operating systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-frwv-8c9x-7766

## What is CVE-2020-9859?

CVE-2020-9859 is a high-severity memory corruption vulnerability in Apple Ipados, published on 5 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A memory consumption issue was addressed with improved memory handling. This issue is fixed in iOS 13.5.1 and iPadOS 13.5.1, macOS Catalina 10.15.5 Supplemental Update, tvOS 13.4.6, watchOS 6.2.6. An application may be able to execute arbitrary code with kernel privileges.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2020-9859?

It affects 5 products.


Products: Apple Ipados, Apple Iphone Os, Apple Mac Os X, Apple Tvos, Apple Watchos.

## How do I fix CVE-2020-9859?

No fix has been published for CVE-2020-9859 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2020-9859 being exploited?

Yes. Attackers have exploited CVE-2020-9859 in the wild since at least 3 Nov 2021.

## Other vulnerabilities in Apple Ipados

- [CVE-2025-43300](https://insights.sbomify.com/CVE-2025-43300/): Apple iOS, iPadOS, and macOS Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24201](https://insights.sbomify.com/CVE-2025-24201/): Apple Multiple Products WebKit Out-of-Bounds Write (critical 10.0, exploited in the wild)
- [CVE-2025-24085](https://insights.sbomify.com/CVE-2025-24085/): Apple Multiple Products Use-After-Free (critical 10.0, exploited in the wild)
- [CVE-2025-31200](https://insights.sbomify.com/CVE-2025-31200/): Apple Multiple Products Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2025-31201](https://insights.sbomify.com/CVE-2025-31201/): Apple Multiple Products Arbitrary Read and Write (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9859 and fix it if it is affected.

What it is: CVE-2020-9859 is a high-severity memory corruption vulnerability in Apple Ipados, published on 5 Jun 2020. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2020-9859 in the wild since at least 3 Nov 2021.

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

## Sources

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

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