dbcve.org
IpadosOperating system · Apple

CVE-2025-24107

HIGH · 7.8 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 11.3 / 15.3 or later.
See remediation →
80/100
Remediation priority · High
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 permissions issue was addressed with additional restrictions. This issue is fixed in iOS 18.3 and iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, watchOS 11.3. A malicious app may be able to gain root privileges.

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 permissions vulnerability in Apple operating systems allowed a malicious application to escalate privileges to root. The issue was addressed through additional permission restrictions in iOS 18.3, iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, and watchOS 11.3.

MitigationApply the vendor security updates: update affected devices to iOS 18.3/iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, or watchOS 11.3 as appropriate for the device type.

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:< 18.3
Iphone OsOperating system
Affected:< 18.3
macOSOperating system
Affected:< 15.3
TvosOperating system
Affected:< 18.3
WatchosOperating system
Affected:< 11.3

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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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. Check iOS or iPadOS version
    On the device, go to Settings > General > About > Version. Note the version number displayed (e.g., 18.2.1).
    Affected if The version is below 18.3 (e.g., 18.2.1, 18.2, 17.x, etc.)
  2. Check macOS version
    Click the Apple menu > About This Mac. Note the version number under the macOS name (e.g., 15.2, 15.1).
    Affected if The version is below 15.3 (e.g., 15.2, 15.1, 14.x, etc.)
  3. Check tvOS version
    On Apple TV, go to Settings > General > About > Version. Note the version number displayed.
    Affected if The version is below 18.3 (e.g., 18.2, 18.1, 17.x, etc.)
  4. Check watchOS version
    On the iPhone, open the Watch app, go to General > About > Watch. Note the version number shown for the watch.
    Affected if The version is below 11.3 (e.g., 11.2, 11.1, 10.x, etc.)

If any Apple device (iPhone, iPad, Mac, Apple TV, or Apple Watch) runs an operating system version lower than the corresponding fixed release (18.3 for iOS/iPadOS/tvOS, 15.3 for macOS, 11.3 for watchOS), the device is affected by this privilege escalation vulnerability.

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 11.3 / 15.3 / 18.3 or later
Fixed in 11.315.318.3
Interim mitigation

Apply the vendor security updates: update affected devices to iOS 18.3/iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, or watchOS 11.3 as appropriate for the device type.

Recommended fix High confidence

iOS 18.3, iPadOS 18.3, macOS Sequoia 15.3, tvOS 18.3, watchOS 11.3

  1. For iOS devices: Go to Settings > General > Software Update and install iOS 18.3
  2. For iPadOS devices: Go to Settings > General > Software Update and install iPadOS 18.3
  3. For macOS: Go to System Settings > General > Software Update and install macOS Sequoia 15.3
  4. For Apple TV: Go to Settings > System > Software Updates and install tvOS 18.3
  5. For Apple Watch: Open the Watch app on iPhone, go to My Watch > General > Software Update and install watchOS 11.3
Caveat Devices running older hardware may not support the latest OS versions; check Apple compatibility lists before upgrading

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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