Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Out-of-bounds write in Apple Model I/O USD file parsing

IdentifiersCVE-2026-20616CWE-787· Out-of-bounds Write

CVE-2026-20616 is an out-of-bounds write vulnerability in Apple's Model I/O component. Apple states that processing a maliciously crafted USD file may lead to unexpected app termination, and that the issue was addressed with improved bounds checking. The vulnerability affects Apple platforms including iOS 18.7.5, iPadOS 18.7.5, macOS Tahoe 26.3, macOS Sonoma 14.8.4, and visionOS 26.3 prior to the fixes. Supporting content also indicates the flaw is associated with parsing of Alembic/USD-related content in Apple's libusd_ms implementation, where insufficient validation of attacker-controlled file data can result in a write past the end of an allocated data structure.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause denial of service via unexpected application termination when a target processes a malicious USD file. Supporting content also suggests that, at least on macOS, the out-of-bounds write may be memory-corruption-capable and could potentially be leveraged for arbitrary code execution in the context of the current process, although Apple's published advisory language for this CVE describes the impact as app termination.

Mitigation

If you can’t patch tonight, do this now.

Until patches are deployed, avoid opening, importing, previewing, or otherwise processing untrusted USD files. Restrict USD file handling to trusted sources, reduce exposure of workflows that automatically parse 3D asset files, and use application sandboxing and content isolation controls where possible to limit impact from malicious file-based inputs.

Remediation

Patch, then assume compromise.

Apply Apple's fixed releases: iOS 18.7.5, iPadOS 18.7.5, macOS Tahoe 26.3, macOS Sonoma 14.8.4, and visionOS 26.3, or later versions that include the fix. The issue was remediated by improved bounds checking in the affected Model I/O parsing path.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
AppleVisionosoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity6

Community discussion across Reddit, Mastodon, and other social sources.