CVE-2025-31200
CVE-2025-31200 is a critical-severity vulnerability in Apple Macos with a CVSS 3.x base score of 9.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2025-04-17). The underlying weakness is classified as CWE-119.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- EPSS exploit prediction: 20% (97th percentile)
- Actively exploited: Yes — listed in CISA KEV (added 2025-04-17)
- EU (EUVD) id: EUVD-2025-11380
- EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2025-04-17)
- Weakness: CWE-119
- Affected product: Apple Macos
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2025-31200?
- 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.
- How severe is CVE-2025-31200?
- CVE-2025-31200 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2025-31200 being actively exploited?
- Yes. CVE-2025-31200 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2025-04-17, which means active exploitation has been confirmed. It should be prioritised for remediation.
- What products are affected by CVE-2025-31200?
- CVE-2025-31200 primarily affects Apple Macos. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2025-31200?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
- Does CVE-2025-31200 have an EU (EUVD) identifier?
- Yes. CVE-2025-31200 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-11380. It is also flagged as exploited in the EUVD (since 2025-04-17).
- When was CVE-2025-31200 published?
- CVE-2025-31200 was published on 2025-04-16 and last updated on 2026-06-17.
References
- https://support.apple.com/en-us/122282
- https://support.apple.com/en-us/122400
- https://support.apple.com/en-us/122401
- https://support.apple.com/en-us/122402
- https://support.apple.com/en-us/122722
- http://seclists.org/fulldisclosure/2025/Apr/26
- http://seclists.org/fulldisclosure/2025/Jun/14
- http://seclists.org/fulldisclosure/2025/May/10
- http://seclists.org/fulldisclosure/2025/Oct/0
- http://seclists.org/fulldisclosure/2025/Oct/4
- https://blog.noahhw.dev/posts/cve-2025-31200/
- https://news.ycombinator.com/item?id=44161894
- https://github.com/JGoyd/iOS-Attack-Chain-CVE-2025-31200-CVE-2025-31201/blob/main/Remote%20Crypto%20Attack%20Chain%20.md
- https://github.com/cisagov/vulnrichment/issues/200
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-31200
Affected products (6)
- cpe:2.3:o:apple:macos:*:*:*:*:*:*:*:*
- cpe:2.3:o:apple:tvos:*:*:*:*:*:*:*:*
- cpe:2.3:o:apple:visionos:*:*:*:*:*:*:*:*
- cpe:2.3:o:apple:ipados:*:*:*:*:*:*:*:*
- cpe:2.3:o:apple:iphone_os:*:*:*:*:*:*:*:*
- cpe:2.3:o:apple:watchos:*:*:*:*:*:*:*:*
More vulnerabilities in Apple Macos
- CVE-2025-43300 — Critical (CVSS 10.0): An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 15.8.5 and iPadOS…
- CVE-2025-24201 — Critical (CVSS 10.0): An out-of-bounds write issue was addressed with improved checks to prevent unauthorized actions. This issue is fixed in…
- CVE-2025-24085 — Critical (CVSS 10.0): A use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3,…
- CVE-2024-44148 — Critical (CVSS 10.0): This issue was addressed with improved validation of file attributes. This issue is fixed in macOS Sequoia 15. An app…
- CVE-2024-44146 — Critical (CVSS 10.0): A logic issue was addressed with improved file handling. This issue is fixed in macOS Sequoia 15. An app may be able to…
- CVE-2023-40455 — Critical (CVSS 10.0): A permissions issue was addressed with additional restrictions. This issue is fixed in macOS Sonoma 14. A sandboxed…
All CVEs affecting Apple Macos →
Other CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) vulnerabilities
- CVE-2026-77946 — Critical (CVSS 10.0): A vulnerability was determined in TRENDnet TEW-821DAP 2.2.01b05. Affected by this vulnerability is the function…
- CVE-2026-76008 — Critical (CVSS 10.0): A flaw has been found in Comfast CF-N1-S 2.6.0.1. This affects the function get_para_from_uri of the file…
- CVE-2026-75784 — Critical (CVSS 10.0): A vulnerability was detected in TRENDnet TEW-WLC100 1v2.07b01. Affected by this issue is the function FUN_0040da4c of…
- CVE-2026-74843 — Critical (CVSS 10.0): A vulnerability was determined in Wavlink WN531P3 and WN535M1 V250922. Affected by this vulnerability is the function…
- CVE-2026-16367 — Critical (CVSS 10.0): Sandbox escape due to invalid pointer in the Disability Access APIs component. This vulnerability was fixed in Firefox…
- CVE-2026-2778 — Critical (CVSS 10.0): Sandbox escape due to incorrect boundary conditions in the DOM: Core & HTML component. This vulnerability was fixed in…