CVE-2025-43387
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.2, macOS Tahoe 26.1. A malicious app may be able to gain root privileges.
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 privilege escalation vulnerability in macOS where a malicious application could bypass permission checks to gain root privileges. The issue was addressed with additional restrictions in macOS Sequoia 15.7.2 and macOS Tahoe 26.1.
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< 15.7.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed macOS versionRun 'sw_vers -ProductVersion' in Terminal or go to Apple menu > About This MacAffected if Version is less than 15.7.2 (for macOS Sequoia) or the system is running any version of macOS older than Sequoia 15.7.2
-
Identify macOS release nameRun 'sw_vers -ProductVersion' and note the major version number (e.g., 15.x = Sequoia, 14.x = Sonoma, 13.x = Ventura, etc.)Affected if Running macOS Sequoia version 15.7.1 or earlier, or any earlier macOS release (Sonoma 14.x, Ventura 13.x, etc.)
-
Confirm system is not a security update branchCheck if the system received the specific 15.7.2 or 26.1 security update by reviewing System Settings > General > Software Update historyAffected if The 15.7.2 or 26.1 security update is not listed as installed
The environment is affected if the installed macOS version is below 15.7.2 (or 26.1 for Tahoe), as the permission bypass vulnerability exists in all prior versions.
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 · scoped15.7.2
Apply macOS Sequoia 15.7.2 or macOS Tahoe 26.1 (or later) security updates to address the permission bypass allowing root privilege escalation.
macOS Sequoia 15.7.2
- Check current macOS version by clicking the Apple menu > About This Mac
- Back up important data using Time Machine or another backup solution
- Open System Settings > General > Software Update
- If macOS Sequoia 15.7.2 or later is available, click Update Now or Download
- Allow the download and installation to complete, restarting when prompted
- After restart, verify the update by checking About This Mac shows version 15.7.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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-2025-43387 — 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-2025-43387 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