Skip to content
major vulnerability· requires attention

Affects broad Apple OS stack; sandbox escape could compromise cross-app data on devices used across industries.

Mobile

CVE-2026-20667

8.8
High
EPSS 0.13%Patch availableFeb 13, 2026

Apple OS sandbox escape risk after logic fix.

common questions

Is CVE-2026-20667 being exploited?

Not confirmed. CVE-2026-20667 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.

How severe is CVE-2026-20667?

CVE-2026-20667 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-20667?

Yes. A fix has been recorded for CVE-2026-20667. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-20667 affect?

CVE-2026-20667 affects watchOS 26.3, macOS Tahoe 26.3, macOS Sonoma 14.8.4, macOS Sequoia 15.7.4, and 2 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-20667?

Apply latest OS updates (26.3+).

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
watchOS 26.3macOS Tahoe 26.3macOS Sonoma 14.8.4macOS Sequoia 15.7.4iOS 26.3iPadOS 26.3
impact

Sandbox escape could allow an app to access data from other apps and system resources.

action required

Immediate action required

affected versions
Apple iOS and iPadOS
  • affected< 26.3
Apple macOS
  • affected< 14.8.4
  • affected< 15.7.4
  • affected< 26.3
Apple watchOS
  • affected< 26.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free