Security readout for executives and security teams
Plain-English summary
Apple fixed a memory corruption flaw across major operating systems. If an attacker already has memory write capability, the flaw may allow arbitrary code execution. Apple reports it may have been used in an extremely sophisticated attack against specific individuals on iOS versions before iOS 26.
Executive priority
Prioritize rapid patching for Apple fleets, especially iPhones used by senior leaders and sensitive personnel. The public evidence points to targeted, sophisticated exploitation rather than mass exploitation, but the potential impact is full code execution once attacker prerequisites are met.
Technical view
CVE-2026-20700 is a CWE-119 memory corruption issue addressed with improved state management. It has CVSS 3.1 score 7.8 with local access, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact. Fixed releases include iOS/iPadOS 26.3, macOS Tahoe 26.3, tvOS 26.3, visionOS 26.3, and watchOS 26.3.
Likely exposure
Exposure is likely on Apple devices running affected OS versions below the fixed releases. The strongest public exploitation signal concerns targeted individuals on iOS before iOS 26. Enterprises with unmanaged BYOD, delayed mobile updates, or high-risk executives should treat exposure as urgent.
Exploitation context
Apple says the issue may have been exploited in an extremely sophisticated attack against specific targeted individuals. CISA KEV status in the provided bundle is false, so broad active exploitation is not established by the sources. The flaw appears more likely to be useful in a chained attack than as a standalone initial access vector.
Researcher notes
Public details are limited. The affected component is not named in the provided sources, and no exploit mechanics are disclosed. The attacker prerequisite is memory write capability, suggesting this CVE may be part of a multi-vulnerability chain. Apple notes related CVEs CVE-2025-14174 and CVE-2025-43529 were issued from the same report.
Mitigation direction
- Update iOS and iPadOS devices to 26.3 or later.
- Update macOS Tahoe systems to 26.3 or later.
- Update tvOS, visionOS, and watchOS devices to 26.3 or later.
- Prioritize executives, journalists, activists, administrators, and other high-risk users.
- Check Apple security guidance for any product-specific follow-up actions.
Validation and detection
- Inventory Apple devices and record OS versions.
- Use MDM compliance data to identify devices below 26.3.
- Confirm high-risk users have completed updates.
- Review Apple security pages for the exact fixed releases.
- Check CISA KEV status periodically for any change.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-20700 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://support.apple.com/en-us/126346CVE reference
- https://support.apple.com/en-us/126348CVE reference
- https://support.apple.com/en-us/126351CVE reference
- https://support.apple.com/en-us/126352CVE reference
- https://support.apple.com/en-us/126353CVE reference
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-20700CVE reference · government-resource
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.