CVE-2026-64725 is an out-of-bounds write vulnerability affecting multiple Apple operating systems. Apple states the issue was addressed through improved bounds checking. A malicious application running on an affected device may be able to trigger the memory corruption condition and cause a denial-of-service. Fixed releases include iOS 18.7.10 and iPadOS 18.7.10, iOS 26.6 and iPadOS 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6, tvOS 26.6, visionOS 26.6, and watchOS 26.6.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small, self-contained proof-of-concept for CVE-2026-64725, an Apple AudioToolboxCore AIFF parsing vulnerability affecting macOS/iOS/iPadOS versions before 26.6. The repo contains four files: a README with reproduction steps and crash output, a Makefile for building the harness and regenerating the sample file, a Python generator that creates a malformed AIFF, and a C harness that exercises the vulnerable public AudioFile API. The exploit capability is limited to local/file-based triggering of an out-of-bounds write. The Python script generates marker_oob.aiff by crafting an AIFF MARK chunk whose declared marker count has the sign bit set (0x8000), while only 64 minimal marker entries are actually present. The C harness then opens the file with AudioFileOpenURL and calls AudioFileGetProperty with kAudioFilePropertyMarkerList, supplying a deliberately undersized heap buffer. According to the README and code comments, the underlying undocumented function AIFFAudioFile::GetMarkerList misinterprets the output size and continues writing 40-byte AudioFileMarker records past the end of the caller buffer, causing heap corruption and an ASan-detectable crash. There is no network behavior, no command execution payload, no persistence, and no attempt to gain code execution. This is a reproducible crash/memory-corruption PoC rather than a weaponized exploit. The repository structure is straightforward: poc/gen_marker_oob_aiff.py creates the malformed input, poc/marker_oob_harness.c is the runtime trigger, and poc/Makefile builds both. The overall purpose is vulnerability reproduction and validation, not exploitation beyond demonstrating the memory safety flaw.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.