Live › vulnerability › CVE-2026-112505
Go to dashboardA bounds-checking flaw in macOS Screen Sharing lets a malicious peer write past a buffer and corrupt process memory. Apple fixed it in macOS Golden Gate 27.2, Sequoia 15.8.2 and Tahoe 26.7.2.
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.
Macs running a macOS release older than the fixed builds where Screen Sharing is enabled and reachable by other hosts. Machines with Screen Sharing off, or only used locally, have a much smaller exposure. The sources do not say which Screen Sharing configuration is required for an attack.
No product ranges from the sources yet.
sw_vers -productVersion and compare against 27.2, 15.8.2 and 26.7.2 for the matching macOS line27.2 (Golden Gate), 15.8.2 (Sequoia) or 26.7.2 (Tahoe) via Software UpdateEach 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. A malicious Screen Sharing peer may be able to corrupt process memory.
This page as .md · .json · in your agent: get_signal("CVE-2026-112505")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.