Live › vulnerability › CVE-2026-112563
Go to dashboardA memory out-of-bounds write in Apple's operating systems can be triggered by processing a maliciously crafted file. The sources say it causes unexpected app termination, which is a crash, and do not report code execution.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 21:20 UTC. All times on this page are UTC.
Any Apple device running the listed versions before the fixed builds can be affected, as the flaw is in the operating system's file processing. The sources do not describe which file types or apps are involved. Devices already on the fixed builds can skip this.
No product ranges from the sources yet.
sw_vers on macOS; compare against the fixed builds listed in the fix.27.2 (Golden Gate), 15.8.2 (Sequoia), or 26.7.2 (Tahoe).27.2 and visionOS to 27.2.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2, tvOS 27.2, visionOS 27.2. Processing a maliciously crafted file may lead to unexpected app termination.
This page as .md · .json · in your agent: get_signal("CVE-2026-112563")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.