# CVE-2020-27950: Apple Multiple Products Memory Initialization

> A malicious application can disclose kernel memory due to a memory initialization issue in Apple operating systems.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Dec 2020
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-76v6-7m6g-p6v4

## What is CVE-2020-27950?

CVE-2020-27950 is a medium-severity vulnerability in Apple Ipados, published on 8 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A memory initialization issue was addressed. This issue is fixed in macOS Big Sur 11.0.1, watchOS 7.1, iOS 12.4.9, watchOS 6.2.9, Security Update 2020-006 High Sierra, Security Update 2020-006 Mojave, iOS 14.2 and iPadOS 14.2, watchOS 5.3.9, macOS Catalina 10.15.7 Supplemental Update, macOS Catalina 10.15.7 Update. A malicious application may be able to disclose kernel memory.

Weakness: CWE-665 (Improper Initialization)

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

It affects 4 products.


Products: Apple Ipados, Apple Iphone Os, Apple Macos, Apple Watchos.

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

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

## Is CVE-2020-27950 being exploited?

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

Public exploit code:

- CVE-2020-27950 exploit (github_poc): https://github.com/synacktiv/CVE-2020-27950
- A Bash script for Kali Linux that exploits an iOS WebKit vulnerability (CVE-2020-27950) using Metasploit and ngrok. Automates payload delivery with a public URL via ngrok, checks for required tools, handles errors, and provides an easy way to crash browsers for educational purposes only. (github_poc): https://github.com/lyonzon2/browser-crash-tool

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

What it is: CVE-2020-27950 is a medium-severity vulnerability in Apple Ipados, published on 8 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2020-27950 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-27950/ (Markdown: https://insights.sbomify.com/CVE-2020-27950/index.md)
```

## Sources

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

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