CVE-2025-31200: Apple Multiple Products Memory Corruption Vulnerability

What it is

A memory corruption issue was addressed with improved bounds checking. This issue is fixed in iOS 18.4.1 and iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, visionOS 2.4.1, watchOS 11.5. Processing an audio stream in a maliciously crafted media file may result in code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS released before iOS 18.4.1.

Exploitation evidence

First exploit evidence seen: 2025-04-17 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2025-04-17. Source

Public exploit code

GitHub proof-of-concept repositories

4 public repositories from 4 accounts, first seen 2025-04-21. Most starred: JGoyd/iOS-Attack-Chain-CVE-2025-31200-CVE-2025-31201 (209 stars), view repository.

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: CISA KEV · nomi-sec/PoC-in-GitHub.

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. (source: CISA KEV)

Fixed versions

• apple macos: upgrade to 15.4.1 or later (affected from 15.0)
• apple tvos: upgrade to 18.4.1 or later
• apple visionos: upgrade to 2.4.1 or later
• apple ipados: upgrade to 18.4.1 or later
• apple iphone os: upgrade to 18.4.1 or later
• apple watchos: upgrade to 11.5 or later

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

Vendor advisories and patches

• https://support.apple.com/en-us/122282 (CISA KEV notes)
• https://support.apple.com/en-us/122400 (CISA KEV notes)
• https://support.apple.com/en-us/122401 (CISA KEV notes)
• https://support.apple.com/en-us/122402 (CISA KEV notes)
• https://support.apple.com/en-us/122722 (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.
• M1038 Execution Prevention (for T1106, T1059) : Identify and block potentially malicious software executed that may be executed through this technique by using application control tools, like Windows Defender Application Control, AppLocker, or Software Restriction Policies where appropriate.
• M1040 Behavior Prevention on Endpoint (for T1106, T1059) : On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent Office VBA macros from calling Win32 APIs.
• M1033 Limit Software Installation (for T1059) : Prevent user installation of unrequired command and scripting interpreters.
• M1045 Code Signing (for T1059) : Where possible, only permit execution of signed scripts.
• M1042 Disable or Remove Feature or Program (for T1059, T1557) : Disable or remove any unnecessary or unused shells or interpreters.
• M1049 Antivirus/Antimalware (for T1059) : Anti-virus can be used to automatically quarantine suspicious files.
• M1026 Privileged Account Management (for T1059) : When PowerShell is necessary, consider restricting PowerShell execution policy to administrators. Be aware that there are methods of bypassing the PowerShell execution policy, depending on environment configuration. PowerShell JEA (Just Enough Administration) may also be used to sandbox administration and limit what c

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.
• Credential Access: Monitor for credential dumping, unusual LSASS access and sudden authentication from new sources.
• Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.
• Command and Control: Alert on outbound connections from the server to new or rare destinations.

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.