CVE-2025-24120
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 by improved management of object lifetimes. This issue is fixed in macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3. An attacker may be able to cause unexpected app 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 confidenceA memory management vulnerability in macOS stemming from improper object lifetime handling allows a remote attacker to cause unexpected application termination (denial of service). The issue is exploitable over the network with low complexity, leading to application crashes.
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.7.3>= 14.0, < 14.7.3>= 15.0, < 15.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 macOS versionRun 'sw_vers -productVersion' in Terminal to retrieve the installed macOS version numberAffected if The version is less than 13.7.3, OR between 14.0 and 14.7.2 inclusive, OR between 15.0 and 15.2 inclusive
-
Confirm full version stringRun 'system_profiler SPSoftwareDataType' and look for the System Version entry to confirm the exact macOS release (e.g., Ventura 13.7, Sonoma 14.7.2, Sequoia 15.2)Affected if The specific release number falls within any of the vulnerable ranges listed above
-
Verify patch stateCheck Apple Security Updates (apple.com/support/security) for the installed macOS release to confirm whether the fix (Ventura 13.7.3, Sonoma 14.7.3, or Sequoia 15.3) has been appliedAffected if The installed version does not match or exceed the fixed releases for the respective macOS generation
The environment is affected if the running macOS version is below 13.7.3, between 14.0-14.7.2, or between 15.0-15.2; otherwise it is not affected.
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.314.7.315.3
Apply the macOS security updates: Sequoia 15.3, Sonoma 14.7.3, or Ventura 13.7.3 depending on the installed macOS version.
macOS Ventura 13.7.3 / macOS Sonoma 14.7.3 / macOS Sequoia 15.3 (depending on current version)
- Check the currently installed macOS version by clicking the Apple menu and selecting 'About This Mac'
- If running macOS Ventura (13.x), upgrade to version 13.7.3 or later
- If running macOS Sonoma (14.x), upgrade to version 14.7.3 or later
- If running macOS Sequoia (15.x), upgrade to version 15.3 or later
- To upgrade, go to System Settings > General > Software Update and install the available update
- Restart the system after the update is installed
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-24120 — 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-24120 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