dbcve.org
macOSOperating system · Apple

CVE-2026-28925

HIGH · 7.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 14.8.7 / 15.7.7 or later.
See remediation →
84/100
Remediation priority · High
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
A buffer overflow was addressed with improved bounds checking. This issue is fixed in macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5. An app may be able to cause unexpected system termination or write 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

Kernel-level buffer overflow vulnerability in macOS (affecting Sequoia 15.7.7, Sonoma 14.8.7, and Tahoe 26.5) that allows a malicious application to potentially write to kernel memory or cause system crash. The flaw was in bounds checking logic within a kernel component.

MitigationApply the available macOS security updates (15.7.7, 14.8.7, or 26.5 depending on version) to patch the kernel memory corruption vulnerability. Prioritize systems running affected macOS versions in enterprise environments.

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:>= 14.0, < 14.8.7>= 15.0, < 15.7.7>= 26.0, < 26.5

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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
    Run 'sw_vers -productVersion' in Terminal or go to Apple menu > About This Mac > System Report > Software > System Version
    Affected if The version falls within 14.0-14.8.6, 15.0-15.7.6, or 26.0-26.4 (not 14.8.7, 15.7.7, or 26.5+)

Your macOS version is affected if it is 14.0 through 14.8.6, 15.0 through 15.7.6, or 26.0 through 26.4, because the vulnerability exists in those version ranges and the fix is in 14.8.7, 15.7.7, and 26.5.

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 14.8.7 / 15.7.7 / 26.5 or later
Fixed in 14.8.715.7.726.5
Interim mitigation

Apply the available macOS security updates (15.7.7, 14.8.7, or 26.5 depending on version) to patch the kernel memory corruption vulnerability. Prioritize systems running affected macOS versions in enterprise environments.

Recommended fix High confidence

macOS Sonoma 14.8.7 / macOS Sequoia 15.7.7 / macOS Tahoe 26.5 (depending on which major version is currently running)

  1. Check the current macOS version by clicking the Apple menu and selecting About This Mac
  2. Back up important data before performing any system update
  3. For macOS 14.x (Sonoma) users: Update to macOS Sonoma 14.8.7 or later via System Settings > General > Software Update
  4. For macOS 15.x (Sequoia) users: Update to macOS Sequoia 15.7.7 or later via System Settings > General > Software Update
  5. For macOS 26.x (Tahoe) users: Update to macOS Tahoe 26.5 or later via System Settings > General > Software Update
  6. After updating, restart the system to ensure the kernel patch is fully applied
Caveat Standard macOS point updates typically have minimal compatibility issues; ensure third-party kernel extensions are compatible

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

Fix this in macOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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