dbcve.org
macOSOperating system · Apple

CVE-2025-24235

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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
A memory initialization 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. A remote attacker may be able to cause unexpected app termination or heap corruption.

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

This is a memory initialization vulnerability in macOS where improper memory handling can be exploited by a remote attacker to cause unexpected application termination or heap corruption. The vulnerability affects macOS Sequoia 15.4, Sonoma 14.7.5, and Ventura 13.7.5, and was addressed through improved memory handling in the security updates.

MitigationApply the available macOS security updates (Sequoia 15.4, Sonoma 14.7.5, or Ventura 13.7.5) to all affected systems to remediate the memory initialization vulnerability.

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
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 checks

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

  1. Identify installed macOS version
    Run 'sw_vers -productVersion' in Terminal to get the exact macOS version number
    Affected if The version displayed is 13.7.5 or earlier (Ventura), 14.7.5 or earlier (Sonoma), or 15.4 or earlier (Sequoia)
  2. Confirm macOS major version
    Run 'uname -r' or check System Settings > About to verify whether the system is running Ventura (13.x), Sonoma (14.x), or Sequoia (15.x)
    Affected if The system runs any of the three affected major versions (13, 14, or 15)
  3. Compare against CVE-affected range
    Cross-reference the installed version with the affected ranges: 13.0 <= version < 13.7.5, 14.0 <= version < 14.7.5, or 15.0 <= version < 15.4
    Affected if The installed version falls within any of these ranges, indicating the unpatched vulnerability is present

A system is affected if it runs macOS Ventura below 13.7.5, Sonoma below 14.7.5, or Sequoia below 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 available macOS security updates (Sequoia 15.4, Sonoma 14.7.5, or Ventura 13.7.5) to all affected systems to remediate the memory initialization vulnerability.

Recommended fix High confidence

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

  1. Back up your Mac using Time Machine or another backup solution before updating
  2. Open System Settings (System Preferences on older macOS versions)
  3. Navigate to General > Software Update
  4. Wait for macOS to check for available updates
  5. If macOS Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4 is available, click Download and Install
  6. Follow the on-screen prompts and allow the installation to complete - the Mac will restart
  7. After the update completes, verify the installed version by checking System Settings > General > About
Caveat Standard macOS update - no major breaking changes expected; ensure compatible applications before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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