dbcve.org
IpadosOperating system · Apple

CVE-2025-24243

HIGH · 7.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 →
81/100
Remediation priority · High
No privileges

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
The 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, watchOS 11.4. Processing a maliciously crafted file may lead to arbitrary code execution.

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

A memory handling vulnerability in multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows arbitrary code execution when processing a maliciously crafted file. The flaw was addressed with improved memory handling in the patched versions.

MitigationUpdate all affected Apple devices to the fixed versions: iOS 18.4/iPadOS 18.4/17.7.6, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4.

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
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 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 device operating system
    Determine which Apple operating system is running on the device (iOS, iPadOS, macOS, tvOS, visionOS, or watchOS)
    Affected if The device runs any of the affected Apple operating systems listed in the CVE
  2. Check iOS or iPadOS version
    On iPhone or iPad, go to Settings > General > About > Version and note the version number
    Affected if The version is less than 17.7.6, or is 18.0 through 18.3.x (meaning version is < 18.4)
  3. Check macOS version
    On Mac, click Apple menu > About This Mac and note the version number (such as 13.x, 14.x, or 15.x)
    Affected if The version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x (meaning version is < 13.7.5, < 14.7.5, or < 15.4)
  4. Check tvOS or visionOS version
    On Apple TV, go to Settings > General > About > Version. On Vision Pro, go to Settings > General > About > Version
    Affected if For tvOS, version is less than 18.4. For visionOS, version is less than 2.4

A device is affected if its installed Apple operating system version falls within any of the vulnerable version ranges listed for that specific platform.

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 / 13.7.5 / 14.7.5 or later
Fixed in 2.413.7.514.7.5
Interim mitigation

Update all affected Apple devices to the fixed versions: iOS 18.4/iPadOS 18.4/17.7.6, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.4, visionOS 2.4, or watchOS 11.4.

Recommended fix High confidence

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

  1. Identify the Apple device type (iPhone, iPad, Mac, Apple TV, or Apple Vision Pro)
  2. Check the current operating system version on the device
  3. For iPhone/iPad: Upgrade to iOS 18.4/iPadOS 18.4, or iPadOS 17.7.6 for older devices
  4. For Mac: Upgrade to macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4 (depending on current macOS version)
  5. For Apple TV: Upgrade to tvOS 18.4
  6. For Apple Vision Pro: Upgrade to visionOS 2.4
  7. Install the update via Settings > General > Software Update (iOS/iPadOS/tvOS/visionOS) or System Settings > Software Update (macOS)
Caveat Standard Apple OS updates may include feature changes; backup device before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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