dbcve.org
macOSOperating system · Apple

CVE-2025-30464

HIGH · 7.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 →
81/100
Remediation priority · High
No privileges

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
An out-of-bounds write issue was addressed with improved bounds checking. 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 or corrupt kernel memory.

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 kernel-level out-of-bounds write vulnerability in macOS where insufficient bounds checking allows an application to write beyond allocated memory boundaries, potentially corrupting kernel memory or causing system termination.

MitigationApply the appropriate macOS security update (Sequoia 15.4, Sonoma 14.7.5, or Ventura 13.7.5) to resolve the bounds checking issue.

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.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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the installed macOS version
    Run 'sw_vers -productVersion' in Terminal to retrieve the currently installed macOS version number
    Affected if The version is less than 13.7.5, or between 14.0 and 14.7.5, or between 15.0 and 15.4 (all of these are vulnerable)
  2. Identify the macOS release name
    Run 'sw_vers -productVersion' and note whether the major version is 13 (Ventura), 14 (Sonoma), or 15 (Sequoia)
    Affected if The specific version range depends on the release name; Ventura versions below 13.7.5, Sonoma versions below 14.7.5, and Sequoia versions below 15.4 are all affected
  3. Confirm kernel vulnerability scope
    This is a kernel-level flaw in the memory management subsystem; no specific kernel extension, configuration, or third-party software needs to be present for the vulnerability to exist
    Affected if If the macOS version falls within any of the affected ranges listed in step 1, the kernel is vulnerable regardless of system configuration

A system is affected if it runs macOS Ventura below 13.7.5, Sonoma below 14.7.5, or Sequoia below 15.4 - no additional configuration checks are required since this is a core kernel bounds-checking issue.

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 (Sequoia 15.4, Sonoma 14.7.5, or Ventura 13.7.5) to resolve the bounds checking issue.

Recommended fix High confidence

macOS Sequoia 15.4 (for macOS 15.x), macOS Sonoma 14.7.5 (for macOS 14.x), or macOS Ventura 13.7.5 (for macOS 13.x)

  1. 1. Check the current macOS version by clicking the Apple menu and selecting 'About This Mac'.
  2. 2. Back up important data using Time Machine or another backup solution before proceeding with the update.
  3. 3. Open System Settings (or System Preferences on older macOS versions).
  4. 4. Navigate to 'General' > 'Software Update'.
  5. 5. Click 'Check for Update' or allow the system to automatically check for updates.
  6. 6. Download and install the appropriate security update: macOS Ventura 13.7.5, macOS Sonoma 14.7.5, or macOS Sequoia 15.4.
  7. 7. Restart the system when prompted to complete the installation.
Caveat Standard macOS update risks apply - ensure backup before upgrading; some legacy applications may be incompatible with newer macOS versions

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

Fix this in macOS Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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