What is the CVSS score of CVE-2025-43402?

CVE-2025-43402 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of macOS are affected by CVE-2025-43402?

CVE-2025-43402 is a high-severity memory corruption vulnerability in macOS kernel that allows authenticated local users to execute arbitrary code or crash systems.

How to fix or mitigate CVE-2025-43402?

Within 24 hours: Inventory all macOS endpoints running Sequoia (pre-15.7.4), Sonoma (pre-14.8.4), or Tahoe (pre-26.1). Within 7 days: Deploy Apple security updates-macOS Sequoia 15.7.4, Sonoma 14.8.4, and Tahoe 26.1-to all affected systems. Within 30 days: Verify patch deployment across 100% of macOS fleet and document remediation completion.

macOS CVE-2025-43402

HIGH

Out-of-bounds Write (CWE-787)

2025-12-12 product-security@apple.com

Apple macOS Memory Corruption Denial Of Service

7.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.8 HIGH

AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Apr 02, 2026 - 19:37 vuln.today

CVE Published

Dec 12, 2025 - 21:15 nvd

HIGH 7.8

DescriptionCVE.org

The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.1. An app may be able to cause unexpected system termination or corrupt process memory.

AnalysisAI

Memory corruption in macOS kernel allows authenticated local users to execute arbitrary code or crash the system. Apple fixed the vulnerability via improved memory handling in macOS Sequoia 15.7.4, Sonoma 14.8.4, and Tahoe 26.1. With CVSS 7.8 (High severity) reflecting local attack vector requiring low privileges, and EPSS at 0.01% (2nd percentile), this represents a moderate real-world risk despite high CVSS scoring. No public exploit identified at time of analysis, and no evidence of active exploitation (not in CISA KEV).

Technical ContextAI

This vulnerability stems from an out-of-bounds write condition (CWE-787) in macOS kernel or system-level components, where improper memory handling allowed applications to write beyond allocated buffer boundaries. The CVSS vector indicates local attack execution (AV:L) with low complexity (AC:L), meaning a malicious application running on the system can reliably trigger the memory corruption without complex preconditions. The CPE designation covers all macOS versions prior to the patches, spanning three major OS releases: Sequoia (15.x), Sonoma (14.x), and the newly released Tahoe (26.x). Out-of-bounds write vulnerabilities in operating system kernels are particularly severe as they operate at privileged execution levels, enabling attackers to bypass security boundaries, corrupt kernel memory structures, or achieve code execution with elevated privileges. Apple's remediation through improved memory handling likely involves bounds checking, memory allocation validation, or migrating to memory-safe programming practices.

RemediationAI

Apple has released security updates addressing this vulnerability across all affected macOS versions. Users should immediately update to macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, or macOS Tahoe 26.1 depending on their current OS release. Updates can be applied through System Settings > General > Software Update on macOS Ventura and later, or System Preferences > Software Update on earlier versions. Enterprise administrators should deploy these updates through their mobile device management (MDM) solutions or Apple Software Update services. Complete vendor security advisories and update instructions are available at https://support.apple.com/en-us/125634, https://support.apple.com/en-us/126349, and https://support.apple.com/en-us/126350. No workarounds are available for this kernel-level memory corruption issue-patching is the only effective mitigation. Organizations unable to immediately patch should implement compensating controls including application allowlisting to prevent execution of untrusted applications, enhanced monitoring for system crashes or memory corruption indicators, and restricted local user privileges on sensitive systems.