CVE-2025-24086
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 · uneditedThe issue was addressed with improved memory handling. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.4, macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3, tvOS 18.3, visionOS 2.3, watchOS 11.3. Processing an image may lead to a denial-of-service.
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 confidenceA denial-of-service vulnerability exists in multiple Apple operating systems where processing a maliciously crafted image leads to a crash due to improper memory handling. The vulnerability is fixed in the listed iOS, iPadOS, macOS, tvOS, visionOS, and watchOS versions.
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< 17.7.4>= 18.0, < 18.3< 18.3< 13.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3< 18.3< 2.3< 11.3CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS version on iPhoneGo to Settings > General > About > Version, or use Finder/iTunes to view the iOS versionAffected if Version is lower than 18.3 or between 17.x versions lower than 17.7.4
-
Check iPadOS version on iPadGo to Settings > General > About > Version, or use Finder/iTunes to view the iPadOS versionAffected if Version is lower than 18.3 or between 17.x versions lower than 17.7.4
-
Check macOS version on MacGo to System Settings > About, or run `sw_vers` in TerminalAffected if Version is lower than 13.7.3, or between 14.0 and 14.7.2, or between 15.0 and 15.2
-
Check tvOS version on Apple TVGo to Settings > General > About > VersionAffected if Version is lower than 18.3
-
Check visionOS version on Vision ProGo to Settings > General > About > VersionAffected if Version is lower than 2.3
-
Check watchOS version on Apple WatchOpen the Watch app on iPhone, go to My Watch > General > About, or go to Settings > General > About on the watchAffected if Version is lower than 11.3
A device is affected if its operating system version falls within any of the unpatched ranges listed for that platform, regardless of configuration, since the vulnerability triggers during image processing.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.311.313.7.3
Apply the appropriate security update for each affected Apple platform: iOS 18.3, iPadOS 18.3 or 17.7.4, macOS Sequoia 15.3, Sonoma 14.7.3, or Ventura 13.7.3, tvOS 18.3, visionOS 2.3, or watchOS 11.3.
iOS 18.3/iPadOS 18.3 (or iPadOS 17.7.4), macOS Ventura 13.7.3/Sonoma 14.7.3/Sequoia 15.3, tvOS 18.3, visionOS 2.3, watchOS 11.3
- Identify the current version of the affected Apple device (iOS, iPadOS, macOS, tvOS, visionOS, or watchOS)
- Determine which product category the device falls into based on the version numbers
- Back up the device data before performing the upgrade
- For iPhone/iPad: Go to Settings > General > Software Update and install the appropriate update (iOS 18.3 for iPhone, iPadOS 18.3 or 17.7.4 for iPad)
- For Mac: Open System Settings > General > Software Update and install the appropriate update (macOS Ventura 13.7.3, Sonoma 14.7.3, or Sequoia 15.3)
- For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.3
- For Apple Watch: On the iPhone, open the Watch app, go to My Watch > General > Software Update and install watchOS 11.3
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.3
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24086 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24086 in production — separate from our analysis above.
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.
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.
- 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