CVE-2026-28892
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 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 · moderate confidenceA permissions vulnerability in macOS allowed an application to modify protected parts of the file system, likely bypassing System Integrity Protection (SIP) or similar access controls. The fix involved removing the vulnerable code path. This is a local privilege escalation issue where a malicious or compromised application could alter system-protected directories.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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.
-
Determine installed macOS versionRun 'sw_vers -productVersion' in Terminal or go to Apple menu > About This MacAffected if Version is 14.x, 15.x, or 26.x (the major versions listed in affected ranges)
-
Compare against affected version rangesCheck if version is >= 14.0 and < 14.8.5, OR >= 15.0 and < 15.7.5, OR >= 26.0 and < 26.4Affected if Version falls within any of these ranges indicates the unpatched version is present
-
Verify patch level for your major versionConfirm the specific subversion: Sonoma should be 14.8.5+, Sequoia should be 15.7.5+, Tahoe should be 26.4+Affected if Running any version below these thresholds means the vulnerability is present
Your environment is affected if the installed macOS version is lower than 14.8.5 (Sonoma), 15.7.5 (Sequoia), or 26.4 (Tahoe) depending on your macOS major version.
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 updates: Sequoia 15.7.5, Sonoma 14.8.5, or Tahoe 26.4 depending on the macOS version in use. This is a standard OS patch requiring no custom code changes.
macOS Sonoma 14.8.5 (for systems on 14.x), macOS Sequoia 15.7.5 (for systems on 15.x), or macOS Tahoe 26.4 (for systems on 26.x)
- Back up your Mac using Time Machine or another backup method before proceeding with the update
- Open System Settings (or System Preferences on older macOS versions)
- Click on General in the sidebar, then select Software Update
- Wait for macOS updates to load - the update to the fixed version (14.8.5, 15.7.5, or 26.4 depending on your current major version) should appear
- Click Update Now or Upgrade Now to download and install the security update
- Restart your Mac when prompted to complete the installation
- After restarting, verify the update was installed by returning to Software Update and confirming the system shows no pending updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28892 — 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-28892 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