# CVE-2026-86950: Apple Multiple Products Out-of-Bounds Write

> An out-of-bounds write allows arbitrary code execution via a malicious file, affecting Apple iOS, iPadOS, and macOS users.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 29 Sep 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-3cf3-h799-fjvq

## What is CVE-2026-86950?

CVE-2026-86950 is a high-severity memory corruption vulnerability in Apple Ipados, published on 28 Sep 2026. 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

An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 18.7.11 and iPadOS 18.7.11, iOS 26.7.1 and iPadOS 26.7.1, macOS Sequoia 15.8.1, macOS Tahoe 26.7.1. Processing a maliciously crafted file may lead to arbitrary code execution. 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 27.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 3 products.


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

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

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

## Is CVE-2026-86950 being exploited?

Yes. Attackers have exploited CVE-2026-86950 in the wild since at least 29 Sep 2026.

Public exploit code:

- Runtime exploit monitor for Apple document/image pipelines (iOS/macOS) — EXPMON concept: Frida agent + behavioral rules. First target: the CVE-2026-86950 glyph chain. (github_poc): https://github.com/msuiche/hotcell
- A python tool to detect PDF files exploiting CVE-2026-86950 (github_poc): https://github.com/decalage2/detect_CVE-2026-86950
- https://github.com/34zY/CVE-2026-86950 (github_poc): https://github.com/34zY/CVE-2026-86950
- Out-of-bounds Write (CWE-787) (github_poc): https://github.com/java99999/CVE-2026-86950-POC
- CVE-2026-86950 (github_poc): https://github.com/0xredash/CVE-2026-86950
- Proof of Concept for CVE-2026-86950 (github_poc): https://github.com/jpdagostin0/CVE-2026-86950-POC

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

What it is: CVE-2026-86950 is a high-severity memory corruption vulnerability in Apple Ipados, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2026-86950 in the wild since at least 29 Sep 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-86950/ (Markdown: https://insights.sbomify.com/CVE-2026-86950/index.md)
```

## Sources

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

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