# CVE-2026-20700: Apple Multiple Buffer Overflow

> An attacker with memory write capability can execute arbitrary code on Apple devices, requiring an OS upgrade to mitigate.

- **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 12 Feb 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Feb 2026
- **Updated:** 2 Apr 2026
- **Also known as:** GHSA-j5x8-2r52-c3ff

## What is CVE-2026-20700?

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

### Official description

A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, watchOS 26.3. An attacker with memory write capability may be able to execute arbitrary code. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26. CVE-2025-14174 and CVE-2025-43529 were also issued in response to this report.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2026-20700?

It affects 6 products.


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

## How do I fix CVE-2026-20700?

No fix has been published for CVE-2026-20700 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 5 Mar 2026.

## Is CVE-2026-20700 being exploited?

Yes. Attackers have exploited CVE-2026-20700 in the wild since at least 12 Feb 2026.

Public exploit code:

- https://github.com/R3n3r0/CVE-2026-20700 (github_poc): https://github.com/R3n3r0/CVE-2026-20700
- https://github.com/notthemystery/CVE-2026-20700-POC-that-ll-never-work (github_poc): https://github.com/notthemystery/CVE-2026-20700-POC-that-ll-never-work

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

What it is: CVE-2026-20700 is a high-severity memory corruption vulnerability in Apple Ipados, published on 11 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-20700 in the wild since at least 12 Feb 2026.

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-2026-20700/ (Markdown: https://insights.sbomify.com/CVE-2026-20700/index.md)
```

## Sources

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

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