Apple patches dyld zero-day CVE-2026-20700 used in highly targeted attacks

Apple released iOS 26.3 and related updates on 11 February 2026 to fix CVE-2026-20700, a memory corruption vulnerability in dyld, the dynamic link editor used across its operating systems. Apple said the flaw may have been exploited in an extremely sophisticated attack against specific targeted individuals running versions of iOS before iOS 26. It was Apple’s first disclosed zero-day of 2026.

Technical details

An attacker who already has a memory write primitive may be able to use the bug to execute arbitrary code; Apple addressed it with improved state management. The issue was reported by Google’s threat analysis team. Apple’s advisory links it to two WebKit flaws fixed earlier, CVE-2025-14174 and CVE-2025-43529, which were issued in response to the same report, suggesting the dyld bug was one stage of a multi-step exploit chain. Apple did not explain how the three are connected or who was targeted.

VulnCheck’s Caitlin Condon told CyberScoop the pattern is consistent with highly targeted spyware or surveillance operations against a very small number of people.

Who is affected

Fixes are available in iOS 26.3 and iPadOS 26.3, macOS Tahoe 26.3, tvOS 26.3, watchOS 26.3 and visionOS 26.3. Help Net Security reported that the fix was also expected for older branches (iOS/iPadOS 18.7.5, macOS Sequoia 15.7.4 and macOS Sonoma 14.8.4). The iOS 26.3 release addresses 38 vulnerabilities in total; CVE-2026-20700 is the only one Apple flagged as exploited.

CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 12 February, giving US federal agencies until 5 March 2026 to remediate.

Recommendations

  • Update iPhones, iPads, Macs, Apple Watch, Apple TV and Vision Pro devices to the 26.3 releases (or the corresponding older-branch updates) without delay.
  • Use MDM compliance policies to block devices below the patched versions from corporate resources.
  • For journalists, executives and other high-risk users, consider enabling Lockdown Mode.
  • Ensure the earlier WebKit fixes for CVE-2025-14174 and CVE-2025-43529 are also applied.

Sources