CVE-2025-24178
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 · uneditedThis issue was addressed through improved state management. 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, 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 · high confidenceA sandbox escape vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, watchOS) allows a malicious or compromised application to break out of its sandbox isolation and gain elevated privileges. The vulnerability stems from improper state management in the affected OS components.
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.4< 18.4< 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.4< 18.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your Apple device type and operating systemDetermine whether the device runs iOS (iPhone), iPadOS (iPad), macOS (Mac computer), tvOS (Apple TV), or watchOS (Apple Watch). Each has separate version tracking.Affected if The device runs any of the listed Apple operating systems.
-
Check iOS or iPadOS version on mobile devicesOn iPhone or iPad, go to Settings > General > About and note the version number. Compare against: iPadOS < 17.7.6, or >= 18.0 and < 18.4; iOS < 18.4.Affected if iOS or iPadOS version falls below 17.7.6, or is 18.0 through 18.3.x.
-
Check macOS version on Mac computersClick the Apple menu > About This Mac and note the version number. Compare against: macOS Ventura < 13.7.5, or >= 14.0 and < 14.7.5, or >= 15.0 and < 15.4.Affected if macOS version is 13.7.4 or lower; 14.0 through 14.7.4; or 15.0 through 15.3.x.
-
Check tvOS version on Apple TVOn Apple TV, go to Settings > General > About > Version and note the build number. Compare against: tvOS < 18.4.Affected if tvOS version is 18.3.x or lower.
-
Assess application installation exposureDetermine if the device allows installation of apps from untrusted or unknown developers (Settings > General > VPN & Device Management on iOS/iPadOS, or System Settings > Privacy & Security on macOS with unidentified developer apps allowed).Affected if The device permits installation of apps from untrusted sources, enabling the malicious app attack vector for sandbox escape.
A device is affected if it runs any Apple OS version within the ranges listed (iOS < 18.4 or 17.7.6, macOS < 13.7.5/14.7.5/15.4, tvOS < 18.4) and has the potential to run untrusted applications.
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 · scoped13.7.514.7.515.4
Apply the available Apple security updates: iOS 18.4/iPadOS 18.4, iPadOS 17.7.6, macOS Sequoia 15.4/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.4, and watchOS 11.4. Prioritize updates for externally-facing or high-risk devices given the critical CVSS score.
iPadOS 17.7.6 or iPadOS 18.4 | iOS 18.4 | macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4 | tvOS 18.4
- Before updating, back up your device data using iCloud or your computer
- On your iPhone, iPad, or iPod touch: Go to Settings > General > Software Update and install the available update
- On Mac: Go to System Settings > General > Software Update and install the available update
- On Apple TV: Go to Settings > System > Software Updates and enable 'Update Automatically' or select 'Update Now'
- After updating, verify the update was successful by checking Settings > General > About (or System Settings > About on Mac) to confirm the version number matches the fixed release for your device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24178 — 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-24178 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