The short version
- The flaw. Apple patched an out-of-bounds write in CoreGraphics, which handles two-dimensional graphics, image rendering and PDFs. Processing a maliciously crafted file can lead to arbitrary code execution; Apple fixed it with improved bounds checking. It credited Meta Product Security with finding and reporting the issue.
- Exploitation. Apple says it is aware of a report that the flaw may have been exploited in what it calls an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27. It gave no numbers, no success rate and no date for any exploitation.
- The patch. The updates appeared on 28 September for iOS and iPadOS (iPhone 11 and later, recent iPad models) and for Macs on macOS Tahoe and macOS Sequoia. SecurityWeek reports that Apple's advisory suggests attacks have been seen only against iOS, and that iOS 27 and macOS 27 do not appear affected.
- The CVE disagreement. The Hacker News and SecurityWeek track the flaw as CVE-2026-86950. BleepingComputer gives the identifier CVE-2026-20700, which The Hacker News describes as a separate dyld flaw patched in February; BleepingComputer also describes it that way later in the same article.
- Agency status. CISA had not added the flaw to its Known Exploited Vulnerabilities catalogue when SecurityWeek reported on 29 September. SecurityWeek says it would be the ninth Apple flaw added this year.
Timeline
| Date | Event |
|---|---|
| February | Apple patches a dyld memory corruption flaw, CVE-2026-20700, that it says was used in sophisticated attacks. |
| 28 September | Apple releases iOS 26.7.1, iPadOS 26.7.1, macOS Tahoe 26.7.1 and macOS Sequoia 15.8.1 to fix the CoreGraphics flaw. |
| 29 September | SecurityWeek and BleepingComputer publish reports on the patch, including that CISA has not listed the flaw. |
What happened
Apple issued updates for iPhones, iPads and Macs on 28 September to close an out-of-bounds write in CoreGraphics, the framework behind two-dimensional vector graphics, image rendering and text drawing across its operating systems. The bug lets a maliciously crafted file run arbitrary code. Apple says it addressed it with improved bounds checking and credited Meta Product Security with the discovery.
In its advisory Apple said it was aware of a report that the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 27. It did not say how many people were targeted, whether any attempt succeeded, or when exploitation was first seen. SecurityWeek reports that CISA had not added the flaw to its Known Exploited Vulnerabilities catalogue at the time of writing.
The sources do not agree on the tracking number. The Hacker News and SecurityWeek both use CVE-2026-86950 for the CoreGraphics flaw. BleepingComputer labels the same patch as CVE-2026-20700, an identifier The Hacker News gives to a dyld flaw fixed in February, and which BleepingComputer also describes that way further down its own article. Readers matching the flaw against vendor or government catalogues should check both numbers.
Who is affected
The patched versions cover iPhone 11 and later, iPad Pro 12.9-inch third generation and later, iPad Pro 11-inch first generation and later, iPad Air third generation and later, iPad eighth generation and later, and iPad mini fifth generation and later, plus Macs running macOS Tahoe or macOS Sequoia. Apple's wording points to targeted rather than mass exploitation, and SecurityWeek reports that the advisory suggests attacks were observed only against iOS.
Apple has not described how a malicious file reaches a victim. SecurityWeek notes that because CoreGraphics renders PDFs and graphics system-wide, delivery could come through web pages, email attachments or messaging apps, where automatic attachment handling and link previews could allow exploitation without a click. That is the publication's analysis, not an Apple statement, and SecurityWeek says it asked Meta whether the flaw was used through WhatsApp.
Wider context
SecurityWeek draws a parallel with an earlier WhatsApp incident, in which the company said a flaw in its iOS and macOS apps was likely used alongside an Apple ImageIO zero-day in zero-click attacks aimed at fewer than 200 users. It is not known whether the new CoreGraphics flaw was used the same way.
BleepingComputer counts this as Apple's second zero-day exploited in the wild this year, after the February dyld flaw CVE-2026-20700. It also lists a Beats Studio Buds Bluetooth flaw and four vulnerabilities in older iPhones and iPads exploited through the Coruna exploit kit, and notes seven Apple zero-days fixed in the previous year.
What is not known yet
- Who is behind the attacks Apple refers to, and which individuals or organisations were targeted.
- How many people were targeted and whether any of the attempts succeeded.
- How the malicious file is delivered — web page, email attachment, messaging app or something else — and whether WhatsApp was involved.
- When exploitation was first observed.
- Which identifier, CVE-2026-86950 or CVE-2026-20700, will appear in vendor and government vulnerability catalogues for this flaw.
What to do
If you manage Apple devices
- Install the 28 September updates on iPhones, iPads and Macs; Apple's advisory lists the fixed versions, among them iOS 26.7.1.
- Include Macs in the rollout, not just phones: the same flaw is fixed in macOS Tahoe 26.7.1 and macOS Sequoia 15.8.1.
- Confirm the installed version on each device after updating rather than relying on the prompt having been accepted.
- Do not wait for a CISA catalogue listing before patching; SecurityWeek reports the flaw was not listed when it published.
If you use an iPhone, iPad or Mac personally
- Update the device now and restart it so the new version takes effect.
- Check the version number in Settings or System Settings to confirm the update applied.
For everyone else
- Assume a file-processing flaw can be reached through a web page, email attachment or message, since Apple has not said which route was used.
- Treat unexpected attachments and links from unknown senders with caution and avoid opening files you did not ask for.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.