CVE-2025-24165
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 permissions issue was addressed with additional restrictions. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. 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 · moderate confidenceThis is a macOS kernel-level permissions vulnerability that allows a locally-installed application to cause unexpected system termination (kernel panic/DoS). The issue was addressed by implementing additional restrictions in the operating system's permission model.
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>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Determine installed macOS versionClick the Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if The version reported is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3 (falls within any of the vulnerable ranges)
-
Confirm macOS build dateRun 'system_profiler SPSoftwareDataType' in Terminal to see detailed version and build informationAffected if The build version matches an affected release (look for versions before 13.7.5, 14.7.5, or 15.4)
If the system runs any macOS version from 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3, it is vulnerable to local applications causing kernel panics.
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 macOS security updates: update to macOS Sequoia 15.4, Sonoma 14.7.5, Ventura 13.7.5 or later to receive the permission restrictions that prevent apps from triggering system termination.
macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 (depending on current major version)
- Check current macOS version by clicking the Apple menu and selecting About This Mac
- Determine which upgrade path applies based on your current major version (Ventura 13.x, Sonoma 14.x, or Sequoia 15.x)
- Back up important data using Time Machine or another backup method before proceeding with the update
- Open System Settings and navigate to General > Software Update
- Click Check for Updates and allow the system to discover available updates
- Select and install the appropriate security update: macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4
- Restart the Mac when prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24165 — 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-24165 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