CVE-2026-28829
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 with additional restrictions. 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 modify protected parts of the file system.
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 · high confidenceA permissions issue in macOS allowed applications to modify protected parts of the file system due to insufficient restrictions. This was addressed in macOS Sequoia 15.7.5, macOS Sonoma 14.8.5, and macOS Tahoe 26.4 by adding additional permission restrictions.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 installed macOS versionRun `sw_vers -productVersion` in Terminal or go to System Settings > General > About to view the macOS versionAffected if The version shown is 14.0 to 14.8.4 (Sonoma), 15.0 to 15.7.4 (Sequoia), or 26.0 to 26.3 (Tahoe)
-
Verify patch statusCheck if the system has received the latest macOS security update by running `softwareupdate --list` or checking System Settings > General > Software UpdateAffected if The security update (Sonoma 14.8.5, Sequoia 15.7.5, or Tahoe 26.4) is not installed or available
A user is affected if their macOS version falls within 14.0 to 14.8.4, 15.0 to 15.7.4, or 26.0 to 26.3 and the corresponding security patch has not been applied.
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 macOS security update (Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4) to remediate the vulnerability.
macOS Sonoma 14.8.5, macOS Sequoia 15.7.5, or macOS Tahoe 26.4 (depending on current version line)
- 1. Check current macOS version: Click Apple menu → About This Mac
- 2. Back up important data using Time Machine or other backup solution before applying updates
- 3. Open System Settings → General → Software Update
- 4. If an update is available, click Update Now or download and install the update
- 5. Install macOS Sonoma 14.8.5 or later if running version 14.x; install macOS Sequoia 15.7.5 or later if running version 15.x; install macOS Tahoe 26.4 or later if running version 26.x
- 6. Restart the Mac when prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28829 — 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-28829 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