DE EN IT

~/exploited / cve-2026-86950

CVE-2026-86950: Apple Multiple Products

According to CISA this vulnerability is already used in attacks (added on 29 September 2026).

Key facts

CVECVE-2026-86950
VendorApple — Multiple Products
VulnerabilityApple Multiple Products Out-of-Bounds Write Vulnerability
Added29 September 2026
Deadline (US agencies)13 October 2026
Ransomware campaignsunknown

Technical data (NVD, FIRST EPSS)

CVSS base score8.8 (high) · CVSS 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Attack over the network, complexity: low, privileges: none needed, user interaction: required
EPSS (exploitation probability)Probability of exploitation in the next 30 days: 26.17%. Higher than 98% of all scored vulnerabilities (as of 18 November 2026). A low value is no all-clear: CISA already lists this flaw as exploited in attacks.
Weakness type (CWE)CWE-787 — Out-of-bounds Write
Affected versionsipados: < 18.7.11
ipados: >= 26.0, < 26.7.1
iphone os: < 18.7.11
iphone os: >= 26.0, < 26.7.1
macos: < 15.8.1
macos: >= 26.0, < 26.7.1

Description (NVD)

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.

Patches and vendor advisories

Description (CISA)

Apple iOS, macOS, and iPadOS contain an out-of-bounds write vulnerability in CoreGraphics that may lead to arbitrary code execution.

Required action (CISA)

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.

What admins should do now

  1. Affected? Check whether Apple Multiple Products is in use and which version runs (package manager, admin UI, --version).
  2. Apply the vendor patch or workaround as soon as it exists. If that is not possible right away: restrict outside access (firewall, VPN, reverse proxy).
  3. Review logs back to 29 September 2026: unusual logins, new files, unexpected processes, outbound connections.
  4. If you suspect a compromise: isolate the system, rotate credentials, check the last backup from before the incident.

The deadline applies to US federal agencies. It is still a useful yardstick for everyone: when a flaw is attacked in the wild, waiting is not an option.

Sources

New articles by e-mail

One e-mail per new article. No tracking, unsubscribe any time. As a thank-you after confirming: my “Server operations & patching” checklist (PDF).