Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-31200: Memory corruption in Apple CoreAudio

Published Apr 16, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS20.9%98th percentile
CISA KEVYesAdded Apr 17, 2025
In the wildActivePer CISA KEV
Vendor
Apple
IdentifiersCVE-2025-31200CWE-787 · Out-of-bounds Write

CVE-2025-31200 is a memory-corruption vulnerability in Apple's CoreAudio framework. Processing an audio stream in a maliciously crafted media file may trigger code execution because of insufficient bounds checking. The vulnerability affects multiple Apple operating systems, including iOS, iPadOS, macOS Sequoia, tvOS, visionOS, and watchOS. Apple acknowledged a report of possible exploitation in an extremely sophisticated attack against specific targeted individuals running iOS versions earlier than 18.4.1.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation may execute attacker-controlled code during audio-stream processing. The precise execution privileges and whether exploitation independently permits sandbox escape or privilege escalation are not established. Claims of zero-click exploitation, Secure Enclave key theft, and wormable execution are not independently verified.

Mitigation

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

Until updates are installed, reduce exposure through web-content filtering and download restrictions, enforce least privilege, enable applicable platform exploit protections, and use application/script allowlisting and host-based detection and prevention controls. These measures reduce delivery risk or potential impact but are not established as complete workarounds. Discontinue use of affected systems if appropriate vendor fixes or mitigations are unavailable.

Remediation

Patch, then assume compromise.

Update to iOS 18.4.1, iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, visionOS 2.4.1, or watchOS 11.5, or a later supported release containing the fix. Apple corrected the memory-corruption issue through improved bounds checking. For older supported operating-system branches, install the applicable vendor security updates; specific fixed versions for those branches are not available here.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
apple-positional-audio-codec-invalid-headerThis repository is a proof-of-concept (POC) exploit for CVE-2025-31200, a vulnerability in Apple's CoreAudio APAC (Apple Positional Audio Codec) decoder affecting macOS (<15.4.1) and iOS (<18.4.1). The exploit demonstrates how a mismatch between the channel layout tag and the remapping array in the APAC/HOA decoder can lead to out-of-bounds reads and writes, potentially allowing for memory corruption. The repository contains: - 'encodeme.mm': The main exploit code, which crafts a malformed APAC audio file by manipulating the channel layout and remapping array. - 'build_encodeme.sh' and 'run_encodeme.sh': Scripts to build and run the exploit, the latter using LLDB to inject further memory manipulation at runtime. - 'check-mismatch.lldb' and 'run_encodeme_hook.lldb': LLDB scripts to set breakpoints and observe/control the memory state during exploitation. - 'convertme2.swift' and 'getaudiolength.swift': Swift utilities for converting audio and checking file properties. - 'apac.ksy': Kaitai Struct definition for the APAC format, useful for understanding and manipulating the binary structure of APAC files. The exploit is not fully weaponized; it is a research POC that demonstrates the bug and provides a controlled (but not fully arbitrary) write. It requires manual steps and a vulnerable system. No network endpoints are involved; the attack vector is local, requiring the ability to run code and debug on the target system.zhuowei · Disclosed Apr 21, 2025 · c++ · objc++ · localPoCCVE-2025-31200This repository is a proof-of-concept (POC) exploit for CVE-2025-31200, a buffer overflow in Apple's CoreAudio APAC decoder affecting iOS < 18.4.1 and macOS < 15.4.1. The exploit works by generating a malicious APAC audio cookie with mismatched channel counts (global: 4, remapping: 64), which is embedded into an audio file (MP4/M4A). When a vulnerable system processes this file (e.g., via AVAudioPlayer, browser, or email client), it triggers out-of-bounds memory access in the APACChannelRemapper::Process function, causing a crash and potential memory corruption. The repository contains Python scripts for generating the exploit payload (poc.py), creating and verifying malicious audio files (generate_audio.py, create_malicious_mp4.py, test_exploit.py), and utility modules for manipulating APAC cookies (caf_utils.py, parser.py). The exploit is primarily a Denial of Service but could be extended for code execution with advanced payloads. No network endpoints are present; the attack is delivered via crafted media files.hunters-sec · Disclosed Aug 28, 2025 · python · media_file · browser · emailPoC
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
AppleTvosoperating_system
AppleVisionosoperating_system
AppleWatchosoperating_system
FAQ

Frequently asked questions

Is CVE-2025-31200 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 17, 2025.
Is there a public exploit for CVE-2025-31200?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-31200, the earliest disclosed Apr 21, 2025.
Is there a patch for CVE-2025-31200?
Update to iOS 18.4.1, iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, visionOS 2.4.1, or watchOS 11.5, or a later supported release containing the fix. Apple corrected the memory-corruption issue through improved bounds checking.
What products are affected by CVE-2025-31200?
Apple Ipados, Apple Macos, Apple Tvos, Apple Visionos, Apple Watchos, and 1 more.
How severe is CVE-2025-31200?
CVE-2025-31200 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 20.9% (98th percentile) as of Oct 9, 2026.
Activity feed

Recent activity

91 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity71Community discussion across Reddit, Mastodon, and other social sources.