CVE-2026-28828
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 · uneditedA permissions issue was addressed by removing the vulnerable code. 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 sensitive user 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 confidenceThis is a macOS permissions vulnerability that could allow a malicious or compromised application to bypass permission checks and access sensitive user data. The vulnerability was remediated by Apple removing the vulnerable code path. The issue affects macOS Sequoia 15.7.5, Sonoma 14.8.5, and Tahoe 26.4 and earlier versions.
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>= 14.0, < 14.8.5>= 15.0, < 15.7.5>= 26.0, < 26.4CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check the installed macOS version numberOpen Terminal and run: sw_vers -productVersionAffected if The version displayed is within the affected ranges: 14.0 to 14.8.4, 15.0 to 15.7.4, or 26.0 to 26.3
-
Confirm the macOS release nameRun: sw_vers -productVersionExtra or check System Settings > About This Mac to identify if the system is Sonoma, Sequoia, or TahoeAffected if The system runs Sonoma, Sequoia, or Tahoe and the version falls within the vulnerable ranges
-
Verify the exact minor versionRun: system_profiler SPSoftwareDataType | grep "System Version" to see the full version string including build numberAffected if The version string shows a build number earlier than the fixed releases (14.8.5, 15.7.5, or 26.4)
The system is affected if it runs macOS Sonoma 14.0-14.8.4, Sequoia 15.0-15.7.4, or Tahoe 26.0-26.3; it is NOT affected if running 14.8.5, 15.7.5, 26.4 or later.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.8.515.7.526.4
Apply the vendor-supplied macOS security updates (Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4) to patch the vulnerable code. Ensure endpoint protection policies enforce automatic security updates.
macOS Sonoma 14.8.5 (or later), macOS Sequoia 15.7.5 (or later), or macOS Tahoe 26.4 (or later) - choose the appropriate version for your current macOS branch
- Open System Settings (or System Preferences on older macOS versions)
- Click on General in the sidebar
- Click on Software Update
- If an update is available, click Update Now or Download to install the security update
- For macOS 14.x (Sonoma): Ensure you update to macOS 14.8.5 or later
- For macOS 15.x (Sequoia): Ensure you update to macOS 15.7.5 or later
- For macOS 26.x (Tahoe): Ensure you update to macOS 26.4 or later
- Restart your Mac if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-28828 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28828 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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