dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 May 2025.
macOSOperating system · Apple

CVE-2025-31200

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-16
Fix available
A fix is available. Upgrade to 2.4.1 / 11.5 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Memory corruption vulnerability in audio stream processing within Apple's media framework. Processing a maliciously crafted media file triggers improper bounds checking during audio parsing, leading to arbitrary code execution. This is a use-after-free or buffer overflow condition in the audio decoder that was being actively exploited in targeted attacks.

MitigationImmediately update all affected Apple devices (iOS 18.4.1+, iPadOS 18.4.1+, macOS 15.4.1+, tvOS 18.4.1+, visionOS 2.4.1+, watchOS 11.5+) to the patched versions. Given confirmed in-the-wild exploitation, prioritize patching for any devices handling untrusted media files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
macOSOperating system
Affected:>= 15.0, < 15.4.1
TvosOperating system
Affected:< 18.4.1
VisionosOperating system
Affected:< 2.4.1
IpadosOperating system
Affected:< 18.4.1
Iphone OsOperating system
Affected:< 18.4.1
WatchosOperating system
Affected:< 11.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed operating system and exact version
    On macOS, run 'sw_vers' in Terminal to get the version number. On iOS, iPadOS, tvOS, visionOS, or watchOS, go to Settings > General > About and note the version number displayed
    Affected if The device runs macOS 15.0 through 15.4.0, any version of tvOS before 18.4.1, any version of visionOS before 2.4.1, any version of iPadOS before 18.4.1, any version of iOS before 18.4.1, or any version of watchOS before 11.5
  2. Confirm the device has media processing capability
    Verify that apps capable of playing audio or video media files are present and have been used. This includes the native Photos, Music, or Safari apps, or any third-party media player applications
    Affected if The device can parse audio streams from media files, which is the default behavior for media playback applications on Apple platforms

A device is affected if it runs any version within the ranges listed and has the ability to process media files, which is standard functionality on these platforms

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.4.1 / 11.5 / 15.4.1 or later
Fixed in 2.4.111.515.4.1
Interim mitigation

Immediately update all affected Apple devices (iOS 18.4.1+, iPadOS 18.4.1+, macOS 15.4.1+, tvOS 18.4.1+, visionOS 2.4.1+, watchOS 11.5+) to the patched versions. Given confirmed in-the-wild exploitation, prioritize patching for any devices handling untrusted media files.

Recommended fix High confidence

iOS 18.4.1, iPadOS 18.4.1, macOS Sequoia 15.4.1, tvOS 18.4.1, visionOS 2.4.1, watchOS 11.5

  1. For iPhone/iPad: Go to Settings > General > Software Update and install iOS 18.4.1 / iPadOS 18.4.1
  2. For Mac: Go to System Settings > General > Software Update and install macOS Sequoia 15.4.1
  3. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4.1
  4. For Apple Watch: Go to Settings > General > Software Update on the paired iPhone and install watchOS 11.5
  5. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4.1
  6. After updating, verify the version in Settings > General > About to confirm the update was successful
Caveat Standard OS upgrade considerations apply; back up device before updating

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in macOS Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-31200 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-31200 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data