CVE-2025-24085
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 · uneditedA use after free issue was addressed with improved memory management. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.6, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3, watchOS 11.3. A malicious application may be able to elevate privileges. Apple is aware of a report that this issue may have been actively exploited against versions of iOS before iOS 17.2.
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 confidenceA use-after-free vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) that allows a malicious application to elevate privileges to root/administrator level. This is a memory management flaw that was being actively exploited in the wild as a zero-day against iOS versions prior to iOS 17.2.
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.6>= 18.0, < 18.3< 18.3>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Check iOS versionOn the device, go to Settings > General > About and note the version number shown next to 'Version'Affected if Version is below 17.7.6, OR version is 18.0, 18.1, or 18.2 (meaning it is >= 18.0 and < 18.3)
-
Check iPadOS versionOn the iPad, go to Settings > General > About and note the version number shown next to 'Version'Affected if Version is below 17.7.6, OR version is 18.0, 18.1, or 18.2 (meaning it is >= 18.0 and < 18.3)
-
Check macOS versionClick the Apple menu > About This Mac. The version number appears below the macOS name (for example, 14.2, 15.1, etc.)Affected if Version is 13.0 through 13.7.4, OR 14.0 through 14.7.4, OR 15.0 through 15.2 (check against the ranges >= 13.0 and < 13.7.5, >= 14.0 and < 14.7.5, >= 15.0 and < 15.3)
-
Check tvOS versionOn Apple TV, go to Settings > General > About > Version to see the installed tvOS versionAffected if Version is below 18.3 (any version from 16.x, 17.x, or 18.0-18.2)
-
Check visionOS versionOn the Vision Pro, go to Settings > General > About to view the visionOS version numberAffected if Version is below 2.3 (any version 1.x or 2.0-2.2)
-
Check watchOS versionOpen the Watch app on the paired iPhone, go to General > About, or on Apple Watch go to Settings > General > About. The version is listed next to 'watchOS'Affected if Version is below 11.3
If your device runs any of the affected Apple OS versions listed above, you are potentially affected by this privilege escalation vulnerability.
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.5
Apply the available security updates immediately: iOS 18.3 or iPadOS 17.7.6 and later, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5 and later, tvOS 18.3, visionOS 2.3, and watchOS 11.3. Prioritize iOS devices given confirmed active exploitation.
Upgrade to the fixed version for your device: iOS 18.3/iPadOS 18.3/iPadOS 17.7.6, macOS 13.7.5/14.7.5/15.3, tvOS 18.3, visionOS 2.3, or watchOS 11.3
- Identify the Apple device type (iPhone, iPad, Mac, Apple TV, Apple Vision Pro, or Apple Watch)
- Determine the current installed version of the operating system
- For iPhone: Upgrade to iOS 18.3 or later
- For iPad: Upgrade to iPadOS 18.3 (if on iPadOS 18.x) or iPadOS 17.7.6 (if on iPadOS 17.x)
- For Mac: Upgrade to macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.3 depending on current macOS version
- For Apple TV: Upgrade to tvOS 18.3
- For Apple Vision Pro: Upgrade to visionOS 2.3
- For Apple Watch: Upgrade to watchOS 11.3
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24085 — 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 sources- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- support.apple.com
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- seclists.org
- github.com
- github.com
- www.cisa.gov
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24085 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