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

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

Which versions of Apple macOS are affected by CVE-2025-46281?

Apple macOS versions Sequoia (prior to 15.7.4), Sonoma (prior to 14.8.4), and Tahoe (prior to 26.2) contain a sandbox escape vulnerability (CVE-2025-46281, CVSS 8.8) allowing locally executing…

How to fix or mitigate CVE-2025-46281?

Within 24 hours, inventory all macOS endpoints to identify systems running Sequoia prior to 15.7.4, Sonoma prior to 14.8.4, or Tahoe prior to 26.2, and quarantine or isolate critical systems from networks where operationally feasible. Within 7 days, deploy application allowlisting controls or endpoint detection and response (EDR) tools to all affected systems to restrict unauthorized application execution and monitor for suspicious process behavior. Within 30 days, monitor Apple security advisories continuously and prepare an expedited patching plan to deploy Sequoia 15.7.4+, Sonoma 14.8.4+, or Tahoe 26.2+ as soon as vendor updates become available, with prioritization for systems holding sensitive data.

Apple macOS CVE-2025-46281

HIGH

Protection Mechanism Failure (CWE-693)

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

Information Disclosure Apple

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

vuln.today AI

8.8 HIGH

Local attack vector with low-privilege app execution required; Scope:Changed reflects sandbox-to-host-OS boundary crossing with full C/I/A impact on the host.

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

4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Aug 21, 2026 - 01:28 vuln.today

CVE Published

Dec 17, 2025 - 21:16 nvd

HIGH 8.8

DescriptionNVD

A logic issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26.2. An app may be able to break out of its sandbox.

AnalysisAI

Sandbox escape in Apple macOS allows a locally executing app with standard user privileges to break out of its sandbox confinement and access host system resources beyond its permitted scope. Affects macOS Sequoia prior to 15.7.4, macOS Sonoma prior to 14.8.4, and macOS Tahoe prior to 26.2, with all versions covered by CPE cpe:2.3:o:apple:macos:*:*:*:*:*:*:*:*. No public exploit code and no CISA KEV listing have been identified at time of analysis, though the CVSS 8.8 score with Scope:Changed reflects the significant cross-boundary impact potential once a malicious app gains execution.

Technical ContextAI

The macOS sandbox (Seatbelt, built on mandatory access controls via the kernel extension sandbox-exec) enforces process-level confinement by evaluating policy rules at system call boundaries. CWE-693 (Protection Mechanism Failure) identifies the root cause class: a security control exists but fails to enforce its intended boundaries due to flawed logic rather than an absent control. Apple describes this specifically as 'a logic issue addressed with improved checks,' consistent with an incorrect policy decision or boundary validation gap in the sandbox enforcement path. CPE cpe:2.3:o:apple:macos:*:*:*:*:*:*:*:* confirms all macOS versions across the Sequoia, Sonoma, and Tahoe release lines are in scope. The S:C (Scope Changed) CVSS metric correctly models that exploitation crosses from the confined app container into the broader host macOS environment.

RemediationAI

The primary fix is to update to macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, or macOS Tahoe 26.2 via System Settings > Software Update, as documented in Apple's advisories at https://support.apple.com/en-us/125886, https://support.apple.com/en-us/126349, and https://support.apple.com/en-us/126350. Until patching is complete, restrict app installation sources by enforcing Gatekeeper to 'App Store Only' via System Settings > Privacy & Security, which reduces exposure by limiting which apps can execute on the system - note this does not prevent exploitation by a compromised App Store app or already-installed applications. Deploying MDM policies (e.g., via Jamf or Apple Configurator) to enforce app allowlists on managed fleets provides an additional layer of control with the trade-off of increased administrative overhead. Blocking network connectivity does not mitigate this vulnerability given its local attack vector.