IpadosOperating system · Apple

CVE-2025-24211

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-31

Fix available

A fix is available. Upgrade to 2.4 / 13.7.5 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

This issue was addressed with improved memory handling. This issue is fixed in iOS 18.4 and iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4. Processing a maliciously crafted video file may lead to unexpected app termination or corrupt process memory.

Technical summary

dbcve analysis · moderate confidence

Memory corruption vulnerability in video file processing within Apple operating systems. Processing a maliciously crafted video file triggers improper memory handling, leading to either unexpected app termination (DoS) or process memory corruption that could potentially enable code execution. The vulnerability affects iOS, iPadOS, macOS, tvOS, and visionOS.

MitigationApply the vendor-supplied patches: iOS 18.4, iPadOS 17.7.6 and 18.4, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, and visionOS 2.4. For legacy systems without patches, restrict video file processing to trusted sources and disable automatic video preview where possible.

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

Affected products & versions

NVD · CPE data

IpadosOperating system

Affected:< 17.7.6>= 18.0, < 18.4

Iphone OsOperating system

Affected:< 18.4

macOSOperating system

Affected:>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4

TvosOperating system

Affected:< 18.4

VisionosOperating system

Affected:< 2.4

CVSS breakdown

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?

dbcve checks

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

Identify the Apple operating system

Determine whether the device runs iOS, iPadOS, macOS, tvOS, or visionOS. For iOS/iPadOS, check Settings > General > About > Version. For macOS, click the Apple menu > About This Mac. For tvOS, go to Settings > General > About > Version. For visionOS, check Settings > General > About.

Affected if The device runs any of the listed affected Apple operating systems.
Check the installed iOS version

On iPhone, go to Settings > General > About > Version and note the version number (for example, 18.3.2). Compare your version against the affected ranges: any version below 18.4, or versions 18.0 through 18.3.x.

Affected if The iOS version is below 18.4.
Check the installed iPadOS version

On iPad, go to Settings > General > About > Version and note the version number. Compare against the affected ranges: below 17.7.6, or versions 18.0 through 18.3.x.

Affected if The iPadOS version is below 17.7.6 or is 18.0 to below 18.4.
Check the installed macOS version

Click the Apple menu > About This Mac and note the version (for example, 14.3.1 Sonoma). Compare against affected ranges: 13.0 to below 13.7.5, 14.0 to below 14.7.5, or 15.0 to below 15.4.

Affected if The macOS version falls within 13.0-13.7.4, 14.0-14.7.4, or 15.0-15.3.x.
Check the installed tvOS version

On Apple TV, go to Settings > General > About > Version and note the version number. Compare against the affected range: any version below 18.4.

Affected if The tvOS version is below 18.4.
Check the installed visionOS version

Go to Settings > General > About and note the version number. Compare against the affected range: any version below 2.4.

Affected if The visionOS version is below 2.4.

The environment is affected if the device runs any of the affected Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS) at a version below the fixed releases (iOS/iPadOS/tvOS 18.4, iPadOS 17.7.6, macOS 15.4/14.7.5/13.7.5, visionOS 2.4).

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 2.4 / 13.7.5 / 14.7.5 or later

Fixed in 2.413.7.514.7.5

Interim mitigation

Apply the vendor-supplied patches: iOS 18.4, iPadOS 17.7.6 and 18.4, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, and visionOS 2.4. For legacy systems without patches, restrict video file processing to trusted sources and disable automatic video preview where possible.

Recommended fix High confidence

iOS 18.4, iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.4, visionOS 2.4

1. Identify the affected Apple device (iPhone, iPad, Mac, Apple TV, or Apple Vision Pro)
2. Determine the current installed OS version from Settings > General > About (iOS/iPadOS) or System Settings > About (macOS)
3. For iPhone/iPad: Go to Settings > General > Software Update and install the latest available update (iOS 18.4 or iPadOS 18.4/17.7.6)
4. For Mac: Go to System Settings > General > Software Update and install macOS 15.4 (Sequoia), 14.7.5 (Sonoma), or 13.7.5 (Ventura) depending on your Mac model
5. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.4
6. For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.4
7. After update completes, verify the fix by confirming the device shows the patched OS version

Caveat Standard OS update considerations - backup important data before updating; some legacy apps may not be compatible with newer OS versions

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

Fix this in Ipados Scoped from the published advisory

Consultation1.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,040

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2025-24211 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-24211?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 2.4 / 13.7.5 or later

Severity 9.8 Critical

Exploit likelihood EPSS, next 30 days 1.8%

Affects: Ipados

Remediation

A high-priority fix

Fix this in Ipados 6 hrs · Low

Typical engagement from $1,040

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2025-24211 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References