dbcve.org
macOSOperating system · Apple

CVE-2026-28862

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-25
Fix available
A fix is available. Upgrade to 14.8.5 / 15.7.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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 privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, macOS Tahoe 26.4. An app may be able to access user-sensitive data.

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 privacy vulnerability in macOS where sensitive user data was not properly redacted from log entries, potentially allowing malicious or compromised applications to read system logs and access private user information. The issue stems from insufficient private data redaction in the logging subsystem.

MitigationUpdate to macOS Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4. Developers should also review their application's logging code to ensure no sensitive data is being written to logs without proper redaction.

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.5>= 15.0, < 15.7.5>= 26.0, < 26.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

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

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 macOS version
    Run 'sw_vers -productVersion' in Terminal to get the installed macOS version
    Affected if The version is 14.0 to 14.8.4, 15.0 to 15.7.4, or 26.0 to 26.3 (falls within the affected ranges)
  2. Identify the macOS release name
    Run 'sw_vers -productVersion' and map the version number: 14.x is Sonoma, 15.x is Sequoia, 26.x is Tahoe
    Affected if The installed version corresponds to an affected release (Sonoma, Sequoia, or Tahoe within the vulnerable version range)
  3. Review system logs for sensitive data exposure
    Use 'log show --predicate 'eventMessage contains "sensitive"' --last 24h' or inspect logs via Console app to check for unredacted private user information such as passwords, tokens, personal identifiers, or credentials
    Affected if Logs contain sensitive user data that should have been redacted but was not, indicating the redaction failure is present

The environment is affected if the installed macOS version falls within 14.0-14.8.4, 15.0-15.7.4, or 26.0-26.3, as these versions contain the flawed logging subsystem that fails to properly redact sensitive user data from log entries.

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.5 / 15.7.5 / 26.4 or later
Fixed in 14.8.515.7.526.4
Interim mitigation

Update to macOS Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4. Developers should also review their application's logging code to ensure no sensitive data is being written to logs without proper redaction.

Recommended fix High confidence

macOS Sonoma 14.8.5, macOS Sequoia 15.7.5, or macOS Tahoe 26.4 depending on your current macOS version

  1. Back up your Mac using Time Machine or another backup solution before updating
  2. Connect your Mac to a power source to prevent interruption during the update
  3. Open System Settings (or System Preferences on older macOS versions)
  4. Click on General in the sidebar, then select Software Update
  5. Wait for macOS to check for available updates
  6. Click 'Update Now' or 'Upgrade Now' next to the available macOS update (14.8.5 for Sonoma, 15.7.5 for Sequoia, or 26.4 for Tahoe)
  7. Follow the on-screen instructions to download and install the update
  8. Restart your Mac when prompted to complete the installation
Caveat Standard macOS point updates typically have minimal breaking changes; however, some third-party apps may have compatibility issues

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

Fix this in macOS Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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