CVE-2026-112611: CVE-2026-112611: An out-of-bounds write issue was addressed with improved bounds checking. This issue is fi…

CVE-2026-112611 at a glance

CVE-2026-112611 is a Out-of-Bounds Write vulnerability in the affected product. NVD published it on 2026-10-27. Public exploit code: 1 public GitHub proof-of-concept repository from 1 account, with the earliest exploit evidence dated 2026-10-27. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.23% (percentile 13.9, scored 2026-11-03). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 29/100.

What it is

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.

Exploitation evidence

First exploit evidence seen: 2026-10-27 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2026-10-27. Most starred: Ping-2o/CVE-2026-112611-cg-shading (19 stars), view the Ping-2o/CVE-2026-112611-cg-shading repository on GitHub.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

Detection Generic guidance

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Businesses without a dedicated security person can have LayerLogix watch their computers for threats.