Live › vulnerability › CVE-2026-112611
Go to dashboardAn out-of-bounds write in Apple's PDF processing lets a maliciously crafted PDF corrupt memory on the device. Successful exploitation could lead to code execution, though the sources do not state the outcome beyond memory corruption.
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 that opens PDF files, including through Mail, Safari, Messages or file previews, is in scope per the affected platforms listed. Teams running fleets of Apple devices should confirm the OS build; the sources do not describe a specific configuration that makes a device more exposed.
No product ranges from the sources yet.
26.7.2 or 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.226.7.2 (26.x line) or 27.2 (27.x line)15.8.2 and macOS Tahoe to 26.7.2Each 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 iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. Processing a maliciously crafted PDF file may lead to memory corruption.
This page as .md · .json · in your agent: get_signal("CVE-2026-112611")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.