External risk intelligence

macOS Out-of-Bounds Write Allows Remote System Termination

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-112552

The vulnerability requires the user to connect to a malicious network file server. While technically network-reachable, typical client-side operating system file mounting is generally performed within trusted or controlled network environments rather than being directly exposed to the public internet by design.

Out-of-bounds Write

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability found in macOS systems, specifically related to an out-of-bounds write issue that could allow an attacker to cause unexpected system termination. The vulnerability is accessible over the network without requiring any user interaction or privileges, potentially impacting system stability if exploited. The main concern is confirming the relevance and exposure of this vulnerability to our environment.

  • System crash vulnerability discovered in macOS.
  • Network attack possible; no user action needed.
  • Confirm if our macOS systems are affected.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by setting up a malicious network file server. When a user connects to this server, the vulnerable system may perform an out-of-bounds write, potentially leading to unexpected system termination.

  • Attacker controls a network file server.
  • User connects to the malicious server.
  • Risk of unexpected system termination.

Live Threat

Current exploitation, exposure, and threat context

A network attacker who controls a file server could cause a denial-of-service condition on affected macOS systems by triggering an out-of-bounds write. This could lead to unexpected system termination, interrupting normal operations.

  • System stability.
  • Network file server interaction.
  • Unexpected system termination.

Operational Fix

Recommended remediation, mitigation, and detection steps

Teams responsible for macOS endpoints and network file services should prioritize this vulnerability. The first practical step is to identify all macOS systems, confirm their network reachability, and assess business criticality. Once identified, engaging the system owners to plan a coordinated remediation effort is essential.

  • macOS endpoint and file service owners.
  • Verify network file service exposure.
  • Plan coordinated remediation.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is macOS Golden Gate, Sequoia, and Tahoe?

These are versions of Apple's desktop and laptop operating system. They act as the core platform that manages hardware, software, and file systems. The software includes built-in networking capabilities that allow users to connect to remote storage or network file shares to access and manage their files.

What does an out-of-bounds write mean for CVE-2026-112552?

This vulnerability, classified as CWE-787, occurs when the software writes data beyond the memory space allocated for it. In this case, the system's memory management fails to properly check bounds while interacting with a network server, which can corrupt internal data and force the operating system to shut down unexpectedly.

How is this vulnerability triggered?

An attacker must control a network file server that the victim's machine connects to. The issue is not triggered by simply being on a network or using typical local software; the system must initiate a connection to the specific malicious file server for the memory error to occur.

Do I need to worry about this if my Mac isn't on the public internet?

According to Halo Surface Signal, this vulnerability is considered unlikely to be exploited from the public internet. Because the attack requires connecting to a specific, attacker-controlled file server, it is generally more relevant in environments where users frequently connect to untrusted or external network storage locations.

What is the first step to address CVE-2026-112552?

Start by identifying all macOS devices in your environment running the affected versions. Verify their update status and determine if they frequently connect to external or untrusted network file servers. Prioritize updating these systems to macOS Golden Gate 27.2, Sequoia 15.8.2, or Tahoe 26.7.2 to resolve the memory handling defect.

References