dbcve.org
IpadosOperating system · Apple

CVE-2025-24210

MEDIUM · 5.5 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 2.4 / 13.7.5 or later.
See remediation →
57/100
Remediation priority · Elevated
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 logic error was addressed with improved error 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. Parsing an image may lead to disclosure of user information.

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 · moderate confidence

A logic error in the image parsing component of multiple Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) allows disclosure of user information due to insufficient error handling during image processing.

MitigationUpdate all affected Apple devices to the patched versions: iOS 18.4, iPadOS 17.7.6 or 18.4, 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check iOS version on iPhone
    Go to Settings > General > About > Version, or run 'nsurlsessiond' debugging. For command line, use 'sw_vers' or check /System/Library/CoreServices/SystemVersion.plist
    Affected if Version is less than 18.4 (or between 18.0 and 18.3.x inclusive)
  2. Check iPadOS version on iPad
    Go to Settings > General > About > Version, or run 'sw_vers' via terminal if available
    Affected if Version is less than 17.7.6, or between 18.0 and 18.3.x inclusive
  3. Check macOS version on Mac computers
    Click Apple menu > About This Mac, or run 'sw_vers' in Terminal
    Affected if Version is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x inclusive
  4. Check tvOS version on Apple TV
    Go to Settings > General > About > Version, or use Finder/iTunes to check the device OS version
    Affected if Version is less than 18.4
  5. Check visionOS version on Apple Vision Pro
    Go to Settings > General > About > Version
    Affected if Version is less than 2.4

A user is affected if any of their Apple devices run an OS version that falls within the listed vulnerable ranges for their respective 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 patched versions: iOS 18.4, iPadOS 17.7.6 or 18.4, 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

iPadOS 17.7.6 or 18.4 (depending on major version), iOS 18.4, macOS Ventura 13.7.5 / Sonoma 14.7.5 / Sequoia 15.4, tvOS 18.4, visionOS 2.4

  1. Update iPadOS to version 17.7.6 (for devices on iPadOS 17.x) or 18.4 (for devices on iPadOS 18.x)
  2. Update iPhone to iOS 18.4
  3. Update macOS Ventura to 13.7.5, macOS Sonoma to 14.7.5, or macOS Sequoia to 15.4
  4. Update tvOS to 18.4
  5. Update visionOS to 2.4
  6. After updating, verify the update was successful via Settings > General > Software Update on iOS/iPadOS, or System Settings > Software Update on macOS
Caveat Standard iOS/macOS update considerations - ensure backups exist before updating, some legacy apps may be incompatible 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
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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