macOSOperating system · Apple

CVE-2025-43284

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-29
Fix available
A fix is available. Upgrade to 13.7.7 / 14.7.7 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
An out-of-bounds read was addressed with improved bounds checking. This issue is fixed in macOS Sequoia 15.6, macOS Sonoma 14.7.7, macOS Ventura 13.7.7. 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 confidence

An out-of-bounds read vulnerability in macOS that was addressed with improved bounds checking. The vulnerability allows a malicious application to read memory outside allocated buffers, leading to unexpected system termination (Denial of Service). The issue affects macOS Sequoia, Sonoma, and Ventura and was patched in the respective 15.6, 14.7.7, and 13.7.7 releases.

MitigationApply the available macOS security updates (Sequoia 15.6, Sonoma 14.7.7, or Ventura 13.7.7) to remediate the vulnerability. Organizations should verify that all affected macOS systems have been patched.

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.7>= 14.0, < 14.7.7>= 15.0, < 15.6

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. Check installed macOS version
    Open Terminal and run: sw_vers -productVersion
    Affected if The version returned is 13.0 to 13.7.6, 14.0 to 14.7.6, or 15.0 to 15.5 (any version below 13.7.7, 14.7.7, or 15.6 respectively)

If the system is running any macOS Ventura version below 13.7.7, Sonoma version below 14.7.7, or Sequoia version below 15.6, the vulnerability is present.

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.7 / 14.7.7 / 15.6 or later
Fixed in 13.7.714.7.715.6
Interim mitigation

Apply the available macOS security updates (Sequoia 15.6, Sonoma 14.7.7, or Ventura 13.7.7) to remediate the vulnerability. Organizations should verify that all affected macOS systems have been patched.

Recommended fix High confidence

macOS 13.7.7 (Ventura), 14.7.7 (Sonoma), or 15.6 (Sequoia) depending on current release

  1. Identify the current macOS version by clicking the Apple menu and selecting About This Mac
  2. Determine the appropriate target version based on current macOS: if on Ventura (13.x) upgrade to 13.7.7; if on Sonoma (14.x) upgrade to 14.7.7; if on Sequoia (15.x) upgrade to 15.6
  3. Open System Settings and navigate to General > Software Update
  4. Click Check for Updates and install the available update
  5. Restart the system if prompted to complete the installation
Caveat Point releases typically have minimal compatibility impact; however, ensure critical applications are compatible 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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-43284 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