SECURITYCRITICALCVE-2026-28911

CVE-2026-28911: macOS Critical Memory Corruption via Malicious App

A critical memory corruption vulnerability in macOS allows a malicious application to corrupt memory of a system process. Apple patched the flaw in macOS...

Dylan H.

Security Team

July 28, 2026
2 min read
CVE-2026-28911: macOS Critical Memory Corruption via Malicious App

Critical severity

Rated critical. Prioritise patching — see the remediation guidance below.

Affected Products

  • macOS Sonoma (before 14.8.8)
  • macOS Tahoe (before 26.6)

Overview

CVE-2026-28911 is a critical memory safety vulnerability in macOS with a CVSS base score of 9.8. The flaw exists in how macOS handles memory operations for system processes, and can be exploited by a malicious application to corrupt memory of a system process — potentially leading to privilege escalation, arbitrary code execution, or system instability.

Apple addressed the vulnerability through improved memory handling routines.

Affected Systems

ProductFixed Version
macOS Sonoma14.8.8
macOS Tahoe26.6

Technical Details

The issue stems from insufficient memory safety checks during specific inter-process operations. By crafting a malicious application, an attacker who has already achieved code execution on a target device can trigger the memory corruption condition to escalate privileges or disrupt critical system services.

The vulnerability is classified as a memory corruption issue — one of the most exploitable bug classes on Apple platforms. Apple's advisory notes the issue was addressed with "improved memory handling."

Risk Assessment

  • CVSS Score: 9.8 (Critical)
  • Attack Vector: Local (requires a malicious app to be installed and run)
  • Impact: System process memory corruption — potential privilege escalation or crash
  • Exploit Status: No public exploit reported at time of disclosure
  1. Update macOS immediately to Sonoma 14.8.8 or Tahoe 26.6 via System Settings → General → Software Update
  2. Restrict app installations to trusted sources (Mac App Store or verified developers with notarization)
  3. Review endpoint security policies to ensure only authorized applications run on managed devices
  4. Monitor for unusual process crashes or unexpected privilege changes as indicators of exploitation attempts

References