CVE-2025-24111
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 memory corruption issue was addressed with improved state management. This issue is fixed in iOS 18.3 and iPadOS 18.3, iPadOS 17.7.7, macOS Sequoia 15.3, macOS Sonoma 14.7.5, macOS Ventura 13.7.5, tvOS 18.3, visionOS 2.3, watchOS 11.3. An app may be able to cause unexpected system termination.
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 confidenceMemory corruption vulnerability in Apple operating systems (iOS, iPadOS, macOS, tvOS, visionOS, watchOS) related to improper state management. An attacker with app execution privileges could exploit this to cause unexpected system termination (denial of service).
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.7>= 18.0, < 18.3< 18.3< 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Identify your Apple device OS and versionOn iPhone/iPad: Settings > General > About > Software Version. On Mac: Apple menu > About This Mac > macOS version. On Apple TV: Settings > General > About > Version. On Apple Watch: Settings > General > About > Watch OS. On Apple Vision: Settings > General > About > visionOS.Affected if The installed version falls into any of these ranges: iOS < 18.3, iPadOS < 17.7.7 or >= 18.0 to < 18.3, macOS < 13.7.5 or >= 14.0 to < 14.7.5 or >= 15.0 to < 15.3, tvOS < 18.3, visionOS < 2.3, or watchOS < 11.3
-
Determine if third-party or untrusted apps can be executedCheck if the device allows installation of apps from sources other than the official App Store (Sideloading) or if the device is managed via MDM with restricted app installation policies.Affected if The device permits execution of third-party applications, as the CVE states an attacker needs 'app execution privileges' to exploit this vulnerability
-
Confirm the specific OS build variantLocate the build number (different from the marketing version) in the same About menu as the version number, for precise matching against Apple's security update documentation.Affected if The build number corresponds to an unpatched release within the affected version ranges listed above
Your device is affected if it runs any unpatched version of iOS, iPadOS, macOS, tvOS, visionOS, or watchOS within the affected version ranges and permits execution of third-party 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 · scoped2.311.313.7.5
Apply vendor-supplied patches by updating all affected Apple devices to iOS 18.3/iPadOS 18.3/17.7.7, macOS Sequoia 15.3/Sonoma 14.7.5/Ventura 13.7.5, tvOS 18.3, visionOS 2.3, or watchOS 11.3 as appropriate for each device.
Upgrade to iOS 18.3/iPadOS 18.3 or iPadOS 17.7.7; macOS 13.7.5/14.7.5/15.3; tvOS 18.3; visionOS 2.3; watchOS 11.3 (depending on device type and current major version)
- Identify the current version of the affected Apple operating system on the device
- For iPhone/iPad: Go to Settings > General > Software Update and install the latest available update (iOS 18.3 or iPadOS 17.7.7/18.3 depending on current version)
- For Mac: Go to System Settings > General > Software Update and install macOS 13.7.5, 14.7.5, or 15.3 as applicable
- 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 General > Software Update and install watchOS 11.3
- For Apple Vision Pro: Go to Settings > General > Software Update and install visionOS 2.3
- After updating, verify the new version by checking Settings > General > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24111 — 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-24111 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