CVE-2026-20700
🔴 High In CISA KEVApple iOS and iPadOS, macOS, tvOS, visionOS and watchOS · All below 26.3 on every listed platform: iOS and iPadOS 26.3, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3 and watchOS 26.3
CVSS (Koffei note)
7.8CVSS (v3.1, CVE List)
7.8EPSS (2026-11-18)
1.654%77.06th percentile
CISA KEV
2026-02-12due 2026-03-05
Exploitation
Yes — CISA KEV since 12/02/2026 (SSVC 13/02/2026: exploitation active, automatable no, technical impact total). Apple's own record ties three of this campaign's CVEs to one report: its text says this issue "may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26" and that CVE-2025-14174 and CVE-2025-43529 were also issued in response to this report. Sekoia's report of 04/11/2026 places it as the PAC bypass in the Class B chain, served from
/v1 alongside CVE-2025-43529 as the WebContent RCE, against iOS 18.5. The chain continues into CVE-2025-14174 and CVE-2025-43510 for the sandbox escape and CVE-2025-43520 for kernel read and write. The same boundary caveat as the rest of this campaign: the Plerdy delivery window closed 03/09/2026, 63 days before this run and therefore just outside the 60-day recency test, so the 🔴 rests on the DarkSword kit uploaded to VirusTotal in September 2026, whose exact day Sekoia does not give, and on CISA adding CVE-2024-27834 to KEV on 04/11/2026 off the back of this reportingTimeline
- 11/02/2026CVE record published (CVE List)
- 12/02/2026Added to the CISA KEV catalogue
- 05/03/2026CISA deadline for US federal agencies
Risk
7.8 High (v3.1), assigned by CISA-ADP ; Apple published no score — AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, EPSS 1.679% (76.99th percentile, scored 04/11/2026) (CWE-119 per CISA-ADP ; Apple describes a memory corruption issue addressed with improved state management, where an attacker with memory write capability may execute arbitrary code. As with the other PAC bypass in this campaign, it is not an entry point but the step that turns memory access into execution)
Fix
Yes, since 11/02/2026 — the 26.3 releases above (Apple advisories and the four sibling notes in the record). No workaround: the control is the OS update
Official description
A memory corruption issue was addressed with improved state management. This issue is fixed in iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, watchOS 26.3. An attacker with memory write capability may be able to execute arbitrary code. 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 26. CVE-2025-14174 and CVE-2025-43529 were also issued in response to this report.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H