dbcve.org
macOSOperating system · Apple

CVE-2026-28923

HIGH · 8.8 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 →
90/100
Remediation priority · Urgent
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 logging issue was addressed with improved data redaction. This issue is fixed in macOS Sequoia 15.7.7, macOS Sonoma 14.8.7, macOS Tahoe 26.5. A malicious app may be able to break out of its sandbox.

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 sandbox escape vulnerability in macOS stemming from improper data redaction in logging functionality. A malicious application could exploit the logging issue to break out of its sandbox and potentially gain elevated privileges. The vulnerability affects macOS Sequoia 15.7.7, Sonoma 14.8.7, and Tahoe 26.5 prior to patching.

MitigationApply the vendor-supplied macOS security updates (Sequoia 15.7.7, Sonoma 14.8.7, or Tahoe 26.5 and later) to affected systems. In enterprise environments, deploy updates via MDM with compatibility testing prior to mass rollout.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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
    Run 'sw_vers -productVersion' in Terminal to get the exact macOS version number
    Affected if Version is 14.0 to 14.8.6, 15.0 to 15.7.6, or 26.0 to 26.4 (falls within < 14.8.7, < 15.7.7, or < 26.5)
  2. Verify logging subsystem is active
    Check if system logging is enabled by running 'sudo log show --predicate 'eventMessage contains "sandbox"' --last 1m' to confirm logs are being written
    Affected if Logging is active (this is the default state on macOS, so most installations are affected if version is vulnerable)
  3. Confirm system log accessibility
    Run 'ls -la /var/log/system.log' or use 'log show --system' to verify system logs are readable
    Affected if System logs are readable (the vulnerability exploits improper redaction in these logs)

A system is affected if it runs macOS version 14.0-14.8.6, 15.0-15.7.6, or 26.0-26.4 with the default logging subsystem enabled (which is the standard configuration on macOS).

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 vendor-supplied macOS security updates (Sequoia 15.7.7, Sonoma 14.8.7, or Tahoe 26.5 and later) to affected systems. In enterprise environments, deploy updates via MDM with compatibility testing prior to mass rollout.

Recommended fix High confidence

macOS 14.8.7 (Sonoma), macOS 15.7.7 (Sequoia), or macOS 26.5 (Tahoe) depending on your current major version

  1. 1. Back up your Mac using Time Machine or another backup solution before updating.
  2. 2. Connect your Mac to power and ensure you have a stable internet connection.
  3. 3. Open System Settings (System Preferences on older macOS versions).
  4. 4. Navigate to General > Software Update.
  5. 5. Wait for macOS to check for available updates.
  6. 6. If an update is available, click 'Update Now' or 'Upgrade Now' to install the fixed version: For macOS 14.x (Sonoma) users, install macOS 14.8.7 or later; For macOS 15.x (Sequoia) users, install macOS 15.7.7 or later; For macOS 26.x (Tahoe) users, install macOS 26.5 or later.
  7. 7. Follow the on-screen instructions and allow the Mac to restart as needed to complete the installation.
  8. 8. After updating, verify the installed version by going to System Settings > General > About to confirm you are running a fixed version.
Caveat Standard macOS point release update with minimal risk; standard backup recommended before any system update

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

Fix this in macOS Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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