cve.bz

CVE-2026-86950 Apple Multiple Products Out-of-Bounds Write Vulnerability

8.8 highKEVEPSS 26%

High (8.8) in Apple Multiple Products. In CISA KEV since 2026-09-29. EPSS 26% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
26% (unchanged from 26% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 98th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-29, due 2026-10-13
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-09-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-787 Out-of-bounds Write
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-86950 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-86950?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-86950?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-86950 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-86950

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-86950](https://cve.bz/cve/badge/CVE-2026-86950.svg)](https://cve.bz/cve/CVE-2026-86950)

HTML:

<a href="https://cve.bz/cve/CVE-2026-86950"><img src="https://cve.bz/cve/badge/CVE-2026-86950.svg" alt="CVE-2026-86950"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apple iOS and iPadOSbefore 18.7.11
Apple iOS and iPadOSbefore 26.7.1
Apple macOSbefore 15.8.1
Apple macOSbefore 26.7.1

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

References

Check your stackJSON