CVE-2026-86950

HIGH(8.8)KEVElevated Risk

Apple Multiple Products Out-of-Bounds Write Vulnerability

Description

CVE-2026-86950 is a high-severity out-of-bounds write vulnerability in Apple's operating systems in which processing a maliciously crafted file may lead to arbitrary code execution. Apple addressed the issue with improved bounds checking in iOS 26.7.1 and iPadOS 26.7.1, macOS Sequoia 15.8.1 and macOS Tahoe 26.7.1. Apple states that it is aware of a report that this vulnerability may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27 — the wording Apple reserves for mercenary spyware campaigns rather than commodity crime. CISA has added CVE-2026-86950 to the Known Exploited Vulnerabilities catalog, and its remediation deadline of October 13, 2026 has already passed.

KEV Information

Vendor
Apple
Product
Multiple Products
Date Added
September 29, 2026
Due Date
October 13, 2026
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
2.8
Impact Score
5.9

CWEs

Affected Products

VendorProductVersion
appleipados< 18.7.11; >= 26.0, < 26.7.1
appleiphone os< 18.7.11; >= 26.0, < 26.7.1
applemacos< 15.8.1; >= 26.0, < 26.7.1

References

Weakness Type

CWE-787: Out-of-bounds Write

An out-of-bounds write occurs when software writes data past the boundary of the buffer it was meant to fill, typically through a faulty length check, index calculation or pointer arithmetic. In the affected Apple operating systems, parsing a crafted file drives such a write, and memory beyond the buffer — which can include control flow data such as return addresses, function pointers or heap metadata — is corrupted in a way the attacker can steer towards executing their own code. Apple's fix is described as improved bounds checking, which is the direct correction for this weakness.

Learn more: CWE-787 — Out-of-bounds Write

Impact Analysis

CVE-2026-86950 has a CVSS 3.1 base score of 8.8 (High) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Attack Vector (Network) and Privileges Required (None): the malicious file is delivered remotely — by message, email or web content — and the attacker needs no account or prior access on the device. User Interaction (Required) is the only mitigating metric, and in practice it means the target has to receive and process the file; for the campaigns Apple describes, that step is engineered to be as unremarkable as possible. Attack Complexity (Low) and Confidentiality, Integrity and Availability (all High): successful code execution on a phone or Mac reaches messages, photos, location, microphone and camera, and it can persist or be chained with further flaws to escalate out of the affected process. Apple's phrasing — an extremely sophisticated attack against specific targeted individuals — indicates targeted surveillance rather than mass exploitation, which is why the EPSS score of 1.24% in the 69th percentile stays modest: journalists, activists, officials and executives face the real risk, while everyone else benefits from the same patch.

Exploit Maturity

Apple states directly that it 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, and CISA has added CVE-2026-86950 to the Known Exploited Vulnerabilities catalog; the remediation deadline of October 13, 2026 has already passed, and the entry does not flag use in ransomware campaigns. The references are Apple's own release notes and the corresponding Full Disclosure postings (Sep/89, Sep/90, Sep/91), which reproduce the advisory text rather than exploit code, so no public proof-of-concept is listed. The EPSS score of 1.24% (69th percentile) is above the median but far from the top, which fits the profile precisely: exploitation in targeted operations does not generate the broad scanning and public tooling that drives EPSS upward. The practical reading is that the exploit exists and works, is held closely rather than published, and that patching closes it before the technique inevitably diffuses.

Remediation

  1. Carry out the action CISA requires, immediately. Apply mitigations in accordance with Apple's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV remediation deadline of October 13, 2026 has already passed.
  2. Update every affected device to iOS 26.7.1, iPadOS 26.7.1, macOS Sequoia 15.8.1 or macOS Tahoe 26.7.1, per Apple's release notes (HT 149226, HT 149228, HT 149229). In a managed fleet, push the update as mandatory rather than optional and verify the build number on each device, because deferral settings routinely leave devices behind for weeks.
  3. Enable Lockdown Mode for high-risk users. Apple ships Lockdown Mode precisely for the targeted-attack scenario described here; for journalists, activists, executives and anyone plausibly of interest to a state-level actor, enabling it reduces the file-processing attack surface that this class of vulnerability depends on.
  4. Reduce the chance that a crafted file reaches the device unseen. Filter attachments at the mail gateway, discourage opening files from unknown senders in messaging apps, and in managed environments restrict which apps may handle untrusted file types — user interaction is the required step, so controls that intervene before it are worth having.
  5. Investigate suspected targets rather than assuming cleanliness. If a user is plausibly in scope, preserve a device backup, check for Apple threat notifications on the Apple ID, review device logs and configuration profiles for anomalies, and consider a factory reset with restoration from a known-good backup. Treat an Apple threat notification as the strongest available indicator and act on it directly.

Technical Details

The flaw is an out-of-bounds write reached through file parsing: a maliciously crafted file causes the affected Apple component to write beyond the bounds of its buffer, and Apple's remedy of improved bounds checking indicates a missing or incorrect size validation before the write. Out-of-bounds writes are the most directly weaponizable memory-safety class, because corrupting adjacent memory — return addresses, function pointers, object vtables or allocator metadata — gives an attacker a path to redirect execution, which is how the advisory's arbitrary code execution outcome arises. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H places delivery over the network with no privileges, requires the user to process the file, and records full impact within an unchanged scope — the attacker gains the authority of the process that parsed the file. Apple's note that exploitation was observed on versions of iOS before iOS 27 bounds the known in-the-wild activity to the older branch, but the fix spans iOS and iPadOS 26.7.1 as well as both current macOS lines, so Macs need the same attention as phones.

Frequently Asked Questions

Is CVE-2026-86950 being actively exploited?

Yes. Apple reports awareness that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27, and CISA has added CVE-2026-86950 to the Known Exploited Vulnerabilities catalog with a deadline of October 13, 2026 that has already passed. Use in ransomware campaigns is not recorded, and the EPSS score of 1.24% reflects targeted rather than mass exploitation.

What products are affected by CVE-2026-86950?

CVE-2026-86950 affects iOS and iPadOS before 26.7.1, macOS before 15.8.1 (Sequoia) and macOS 26.0 before 26.7.1 (Tahoe). The fixed releases are iOS 26.7.1, iPadOS 26.7.1, macOS Sequoia 15.8.1 and macOS Tahoe 26.7.1.

How do I fix CVE-2026-86950?

Update to iOS 26.7.1, iPadOS 26.7.1, macOS Sequoia 15.8.1 or macOS Tahoe 26.7.1, following Apple's release notes. In managed fleets, make the update mandatory and verify build numbers rather than relying on user-initiated installation. For users who may be targets of state-level actors, enable Lockdown Mode, which reduces the file-processing attack surface this vulnerability relies on.

How severe is CVE-2026-86950?

CVE-2026-86950 is rated High with a CVSS 3.1 base score of 8.8: remote delivery, no privileges required, and full impact on confidentiality, integrity and availability, with user interaction as the only barrier. Its EPSS score of 1.24% sits in the 69th percentile. For most users the realistic exposure is limited because exploitation has been observed only in targeted attacks, but for individuals of interest to sophisticated adversaries the severity is as high as it gets on a personal device.

CVSS Score

8.8
HIGH(8.8)

EPSS Score

EPSS Score26.17%
EPSS Percentile98.0%

Dates

PublishedSeptember 28, 2026
Last ModifiedOctober 27, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.