dbcve.org
IpadosOperating system · Apple

CVE-2025-24173

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
This issue was addressed with additional entitlement checks. 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. An app may be able to break out of its sandbox.

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 sandbox escape vulnerability in Apple's operating systems allows a maliciously crafted sandboxed application to bypass entitlement checks and break out of its sandbox, potentially gaining unauthorized access to system resources and privileges.

MitigationApply the available security updates (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) to all affected Apple devices.

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.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 your Apple device OS type and version
    On iOS/iPadOS: go to Settings > General > About > Version. On macOS: click Apple menu > About This Mac > Version. On tvOS/visionOS: go to Settings > General > About > Version.
    Affected if The detected version is not listed in the fixed versions (iOS 18.4+, iPadOS 17.7.6 or 18.4+, macOS 13.7.5+, 14.7.5+, 15.4+, tvOS 18.4+, visionOS 2.4+)
  2. Confirm iOS version for iPhone
    If using iPhone, verify the iOS version number from Settings > General > About > Version.
    Affected if iOS version is less than 18.4
  3. Confirm iPadOS version for iPad
    If using iPad, verify the iPadOS version from Settings > General > About > Version.
    Affected if iPadOS version is less than 17.7.6, OR is 18.0 or higher but less than 18.4
  4. Confirm macOS version
    If using Mac, verify macOS version from Apple menu > About This Mac > Version number.
    Affected if macOS version is less than 13.7.5, OR is 14.0-14.7.4, OR is 15.0-15.3.x
  5. Confirm tvOS or visionOS version
    If using Apple TV or Apple Vision Pro, verify the tvOS or visionOS version from Settings > General > About.
    Affected if tvOS version is less than 18.4, OR visionOS version is less than 2.4

Your device is affected if its operating system version falls below the corresponding patched version for your Apple 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

Apply the available security updates (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) to all affected Apple devices.

Recommended fix High confidence

Upgrade to iOS 18.4 / iPadOS 17.7.6 or 18.4 / macOS 13.7.5 / 14.7.5 / 15.4 / tvOS 18.4 / visionOS 2.4 depending on your current version

  1. Determine your current device operating system version via Settings > General > About (iOS/iPadOS) or System Settings/About This Mac (macOS)
  2. For iPhone and iPad: Go to Settings > General > Software Update and install the latest available update (iOS 18.4 or iPadOS 17.7.6/18.4)
  3. For Mac: Open System Settings > General > Software Update and install macOS 13.7.5, 14.7.5, or 15.4 depending on your current macOS version
  4. For Apple TV: Go to Settings > System > Software Updates and update to tvOS 18.4
  5. For Apple Vision Pro: Go to Settings > General > Software Update and update to visionOS 2.4
  6. After updating, verify the security patch was applied by checking the version number in Settings > General > About
Caveat Standard OS update considerations apply - review release notes for feature changes before updating

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

Fix this in Ipados Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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