How to Fix CVE-2026-20700: Denial of Service in iOS and iPadOS

By Sai Kiran Pandrala

Patch immediately. CISA added CVE-2026-20700 to the Known Exploited Vulnerabilities catalog on 2026-02-12. Federal civilian agencies must remediate by 2026-03-05. Treat every internet-reachable instance as a priority patch.

What is CVE-2026-20700?

CVE-2026-20700 is a Denial of Service flaw in Apple iOS and iPadOS. It carries a CVSS base score of 7.8 (high). CISA confirmed real-world exploitation by adding it to the Known Exploited Vulnerabilities catalog on 2026-02-12.

From the source 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.

Why it matters in practice: KEV-listed CVEs draw continuous internet-wide scanning. Any unpatched, internet-reachable installation is on borrowed time. The blast radius depends on how the affected service is exposed. An internet-facing instance with no compensating controls is the highest-risk configuration.

Am I affected?

You are affected if your installation of iOS and iPadOS matches a version listed in the Affected row above.

On macOS or iOS, check the installed version:

sw_vers    # macOS version
system_profiler SPApplicationsDataType | grep -A 3 -i "iOS and iPadOS"

How to fix CVE-2026-20700

Apply the vendor patch. Target a build at or above: 26.3. The runnable command set below covers the most common deployment patterns for iOS and iPadOS.

macOS

# List available updates
softwareupdate --list
# Install all recommended updates
sudo softwareupdate -i -a -R
# For specific app via Homebrew
brew update && brew upgrade

iOS / iPadOS

Settings -> General -> Software Update. Tap Update Now to install the latest build that contains the fix for CVE-2026-20700.

After applying the patch

1. Restart the service or device so the patched binary loads.
2. Confirm the running version matches the Fixed in row using the verification command below.
3. Rotate credentials and API keys that the affected service could access if the asset was exposed during the disclosure window.

If you can't patch immediately

Until the patch lands, narrow the attack surface with these runnable controls.

Apple devices

Until the patched build is installed, avoid opening untrusted documents, links, or attachments that match the attack surface described in the advisory. Restrict the affected app via MDM where possible:

# Vendor advisory: https://support.apple.com/en-us/126346
# macOS - disable Lockdown-Mode-style hardening if you cannot patch
# (use MDM payload com.apple.security.lockdown or sudo profiles install -path <profile>.mobileconfig)
sudo profiles install -path "/path/to/restrict-ios.mobileconfig"

Mitigations are temporary. Apply the vendor patch as soon as a maintenance window opens.

How to verify the fix worked

Confirm the patched build is the one actually running.

sw_vers
softwareupdate --history | tail -5

Expected: the build number matches Apple's release notes for 26.3.

Also worth doing: pull recent log windows for any indicators of compromise listed in the vendor advisory, and re-run an authenticated vulnerability scan with up-to-date signatures.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-28905: Improper Restriction of Operations within the Bounds of a Memory Buffer in Safari — Improper Restriction of Operations within the Bounds of a Memory Buffer in Safari
• How to Fix CVE-2026-20624: Critical Vulnerability in macOS — Critical Vulnerability in macOS
• How to Fix CVE-2026-28828: Critical Vulnerability in macOS , Critical Vulnerability in macOS
• How to Fix CVE-2026-28826: Critical Vulnerability in macOS , Critical Vulnerability in macOS
• How to Fix CVE-2026-20675: Critical Vulnerability in iOS and iPadOS , Critical Vulnerability in iOS and iPadOS

Is CVE-2026-20700 being exploited in the wild?

Yes. CISA added CVE-2026-20700 to the Known Exploited Vulnerabilities catalog on 2026-02-12. KEV listing means at least one confirmed real-world exploitation report exists.

Do I have to take downtime to patch?

For most Apple iOS and iPadOS deployments, the patched build needs a service restart or device reboot. HA pairs and clusters can roll the upgrade by patching the standby first, failing over, then patching the former primary.

Will a WAF or IDS rule alone close CVE-2026-20700?

No. Network filters cut down opportunistic scans but they do not remove the flaw. The vendor patch is the only durable fix.

How quickly should I act on CVE-2026-20700?

Within the standard patch cycle if the asset is internal-only. Inside one to two weeks for any internet-facing instance, sooner if compensating controls are not in place.

References

• Official vendor advisory: https://support.apple.com/en-us/126346
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-20700
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• CISA KEV entry: "Apple Multiple Buffer Overflow Vulnerability" - added 2026-02-12, due 2026-03-05
• Additional reference: https://support.apple.com/en-us/126348
• Additional reference: https://support.apple.com/en-us/126351
• Additional reference: https://support.apple.com/en-us/126352
• Additional reference: https://support.apple.com/en-us/126353

*Assembled from the official vendor advisory, the NVD record, and the CISA KEV listing on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*