CVE-2026-112688: CVE-2026-112688: A memory corruption issue was addressed with improved memory handling. This issue is fixed…

CVE-2026-112688 at a glance

CVE-2026-112688 is a high-severity Memory Corruption vulnerability in Apple Ipados, with a CVSS 3.1 base score of 8.8. NVD published it on 2026-10-27 and classifies the weakness as CWE-119. Public exploit code: 1 public GitHub proof-of-concept repository from 1 account, with the earliest exploit evidence dated 2026-11-02. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.64% (percentile 50.5, scored 2026-11-03). NVD configuration data lists a fixed release for 7 products, for example apple ipados 26.7. CVERadar maps 1 MITRE ATT&CK technique across Execution, inferred from the CWE and the description. Its CVERadar threat level is 48/100.

What it is

A memory corruption issue was addressed with improved memory handling. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27.2 and iPadOS 27.2, macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. Parsing a file may lead to an unexpected app termination or arbitrary code execution.

Exploitation evidence

First exploit evidence seen: 2026-11-02 (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-11-02. Most starred: 0xjohnnydev/CVE-2026-112688-backboardd (10 stars), view the 0xjohnnydev/CVE-2026-112688-backboardd 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

• apple ipados: upgrade to 26.7 or later
• apple ipados: upgrade to 27.2 or later (affected from 27.0)
• apple iphone os: upgrade to 26.7 or later
• apple iphone os: upgrade to 27.2 or later (affected from 27.0)
• apple macos: upgrade to 15.8.2 or later
• apple macos: upgrade to 26.7.2 or later (affected from 26.0)
• apple macos: upgrade to 27.2 or later (affected from 27.0)

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

Vendor advisories and patches

• Apple vendor advisory (support.apple.com) (Release Notes, Vendor Advisory)
• Apple vendor advisory (support.apple.com) (Release Notes, Vendor Advisory)
• Apple vendor advisory (support.apple.com) (Release Notes, Vendor Advisory)
• Apple vendor advisory (support.apple.com) (Release Notes, Vendor Advisory)
• Apple vendor advisory (support.apple.com) (Release Notes, Vendor Advisory)

MITRE ATT&CK mitigations for this chain

• M1050 Exploit Protection (for T1203) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
• M1051 Update Software (for T1203) : Perform regular software updates to mitigate exploitation risk. Keeping software up-to-date with the latest security patches helps prevent adversaries from exploiting known vulnerabilities in client software, reducing the risk of successful attacks.
• M1048 Application Isolation and Sandboxing (for T1203) : Browser sandboxes can be used to mitigate some of the impact of exploitation, but sandbox escapes may still exist. Other types of virtualization and application microsegmentation may also mitigate the impact of client-side exploitation. Risks of additional exploits and weaknesses in those systems may still exist.

Detection Generic guidance

• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

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.

If laptops and desktops fall behind on updates, LayerLogix endpoint security adds detection and response on each device.