Evidence dossier

CVE-2026-20700

CVE-2026-20700

61.876.8Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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.

State
PUBLISHED
Published
Feb 11, 2026
Updated
Apr 2, 2026
Evidence coverage
85%
CISA KEVCatalog member

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

FIRST EPSS1.32%

2026-07-18 · v2026.06.15 · percentile 67.6%

Source stateNo scored conflict

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

appleoriginal assertion
container

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.

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

CISA KEVoriginal assertion
observed_exploitation

Apple Multiple Buffer Overflow Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.013190000000; percentile 0.676390000000

Applicability

Cited product scope

Trace impact →
AppleiOS and iPadOS
[{"status": "affected", "version": "0", "lessThan": "26.3", "versionType": "custom"}]unknown
ApplemacOS
[{"status": "affected", "version": "0", "lessThan": "26.3", "versionType": "custom"}]unknown
AppletvOS
[{"status": "affected", "version": "0", "lessThan": "26.3", "versionType": "custom"}]unknown
ApplevisionOS
[{"status": "affected", "version": "0", "lessThan": "26.3", "versionType": "custom"}]unknown
ApplewatchOS
[{"status": "affected", "version": "0", "lessThan": "26.3", "versionType": "custom"}]unknown
Unknown vendorUnknown product
cpe:2.3:o:apple:ipados:*:*:*:*:*:*:*:*; end excluding 26.3supported
Unknown vendorUnknown product
cpe:2.3:o:apple:iphone_os:*:*:*:*:*:*:*:*; end excluding 26.3supported
Unknown vendorUnknown product
cpe:2.3:o:apple:macos:*:*:*:*:*:*:*:*; end excluding 26.3supported
Unknown vendorUnknown product
cpe:2.3:o:apple:tvos:*:*:*:*:*:*:*:*; end excluding 26.3supported
Unknown vendorUnknown product
cpe:2.3:o:apple:visionos:*:*:*:*:*:*:*:*; end excluding 26.3supported
Unknown vendorUnknown product
cpe:2.3:o:apple:watchos:*:*:*:*:*:*:*:*; end excluding 26.3supported

Assessments

CVSS by origin

7.8
134c704f-9b21-4f2e-91b3-4a467353bcc0CVSS 3.1 · role SecondaryCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8
CISA-ADPCVSS 3.1 · role unknownCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.