CVE Tools

CVE-2026-20700

Exploited in the wild. In CISA KEV since 2026‑02‑12. Fixed in 26.3.

Published Updated Sources: CVE.org, NVD, BDU

What to do

Find your product and version, then upgrade to the build on the right.

  • Apple iOS and iPadOSAffected: < 26.3Upgrade to: 26.3Stated by: CVE record
  • Apple tvOSAffected: < 26.3Upgrade to: 26.3Stated by: CVE record
  • Apple visionOSAffected: < 26.3Upgrade to: 26.3Stated by: CVE record
  • Apple watchOSAffected: < 26.3Upgrade to: 26.3Stated by: CVE record
  • Apple macOSAffected: < 26.3Upgrade to: 26.3Stated by: CVE record

Versions as the sources state them. 1 more product has version data. Full version matrix after sign-in

Steps

Written by AI from the record
  1. Check the installed software version on every managed iPhone, iPad, Mac, Apple TV, Apple Watch, and Vision Pro.
  2. Update affected devices to version 26.3 using Apple’s Software Update settings.
  3. Prioritize devices used by executives, administrators, or staff handling sensitive business data.
  4. Confirm through your device-management reports that every device completed the update.

Coverage timeline

2 publishers
  1. Exploitation reported in the wild

    ·The Hacker News summary
  2. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 2 further articles named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

This is a serious flaw in Apple operating systems before version 26.3; businesses using affected devices should update them now.

CVE-2026-20700 is a high-severity CoreGraphics out-of-bounds write that can enable arbitrary code execution after an attacker obtains memory-write capability.

If you're affected

  • Device takeover
  • Business data exposure
  • Account compromise
  • Service disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS77th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2026-02-12.

US federal agencies must remediate by 2026-03-05.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.7% chance of exploitation activity in the next 30 days, which ranks it in the 77th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Attention now

Sustained.

Lifecycle

7 events over 134 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Patch availablerecord updated
  3. Added to CISA KEV
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.8 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for IPadOS, not every advisory. This one: actively exploited.