Apple Multiple Buffer Overflow Vulnerability
Apple — iOS and iPadOS
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.
7.8
1.3%
Vector breakdown
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- Feb 11, 2026
- Modified
- Apr 2, 2026
- Added to KEV
- Feb 12, 2026
- Federal patch due
- Mar 5, 2026
CISA required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Weakness classification
Proof-of-concept & exploitation references
Weaponization
Public repositories whose name or description references CVE-2026-20700, found via a live GitHub search at request time. These are community-sourced signals, not a verified working exploit - cross-check each one before relying on it, and treat higher star counts and recent activity as (weak) corroboration, not proof.
No public GitHub repositories referencing CVE-2026-20700 were found at last check. Absence here is not proof no exploit exists - see the references below for vendor advisories and write-ups.
References
Frequently asked questions
What is CVE-2026-20700?
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.
How severe is CVE-2026-20700?
CVE-2026-20700 has a CVSS base score of 7.8 out of 10 (CVSS 3.1).
Is CVE-2026-20700 actively exploited in the wild?
Yes. CVE-2026-20700 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added Feb 12, 2026, meaning CISA has confirmed evidence of active exploitation.
What is the EPSS score for CVE-2026-20700?
1.3% - meaning FIRST.org's EPSS model estimates a 1.3% probability this vulnerability will be exploited in the wild within 30 days (68% percentile among all scored CVEs).
What type of vulnerability is CVE-2026-20700?
CVE-2026-20700 is classified under CWE-119 (CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer).
Cross-checked against
Impactr finds and proves whether CVE-2026-20700 - or flaws like it - are actually reachable in your own web apps and APIs, with a reproducible exploit as evidence.
Join the waitlist