dbcve.org
macOSOperating system · Apple

CVE-2025-24260

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 13.7.5 / 14.7.5 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An attacker in a privileged position may be able to perform a denial-of-service.

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

Memory handling vulnerability in macOS allowing a privileged attacker to cause denial-of-service. The issue is fixed via OS updates in macOS Sequoia 15.4, Sonoma 14.7.5, and Ventura 13.7.5.

MitigationApply the appropriate macOS security update (15.4, 14.7.5, or 13.7.5) to affected systems. Since the attacker requires privileged position, prioritize patching endpoints with elevated access.

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
macOSOperating system
Affected:>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed macOS version via Terminal
    Open Terminal and run: sw_vers -productVersion
    Affected if The version output is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x (any version below 13.7.5, 14.7.5, or 15.4 respectively)
  2. Check macOS version via System Settings
    Go to Apple menu > Settings > About (or System Settings > About on newer versions) and note the Version number displayed
    Affected if The displayed version falls within any of the affected ranges: 13.x before 13.7.5, 14.x before 14.7.5, or 15.x before 15.4
  3. Verify build number for precise version tracking
    Open Terminal and run: uname -r or check System Settings > About > Build Number
    Affected if The build number corresponds to an unpatched version in the affected ranges listed above
  4. Confirm system is not receiving this vulnerability in Apple security updates
    Check System Settings > General > Software Update to confirm the installed version matches or exceeds the fixed releases (13.7.5, 14.7.5, or 15.4)
    Affected if The system shows no available updates but remains on a version below the fixed releases, indicating it may be affected

A system is affected if it runs any macOS version from 13.0 up to but not including 13.7.5, 14.0 up to but not including 14.7.5, or 15.0 up to but not including 15.4.

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 13.7.5 / 14.7.5 / 15.4 or later
Fixed in 13.7.514.7.515.4
Interim mitigation

Apply the appropriate macOS security update (15.4, 14.7.5, or 13.7.5) to affected systems. Since the attacker requires privileged position, prioritize patching endpoints with elevated access.

Recommended fix High confidence

macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4 (depending on your current macOS version)

  1. Back up your Mac using Time Machine or another backup method before applying updates
  2. Open System Settings (or System Preferences on older macOS versions)
  3. Navigate to General → Software Update
  4. Allow macOS to check for available updates
  5. If an update is available, click 'Update Now' or 'Upgrade Now' to download and install the security update
  6. Restart your Mac when prompted to complete the installation
  7. After restarting, verify the update was successful by returning to System Settings → General → Software Update
Caveat Standard macOS point releases typically do not introduce breaking changes; however, ensure compatibility with critical applications before updating

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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