CVE-2025-46310
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 · uneditedThis issue was addressed through improved state management. This issue is fixed in macOS Sequoia 15.7.4, macOS Sonoma 14.8.4, macOS Tahoe 26. An attacker with root privileges may be able to delete protected system files.
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 state management flaw in macOS allowed attackers with root privileges to delete protected system files that should have been shielded from even administrative removal. The vulnerability stemmed from improper handling of file protection state, enabling root users to bypass intended safeguards on critical system files.
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.4>= 15.0, < 15.7.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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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 click Apple menu > About This Mac to view the version numberAffected if The version is 14.0 through 14.8.3, or 15.0 through 15.7.3 (any version in the ranges >= 14.0 < 14.8.4 or >= 15.0 < 15.7.4)
-
Confirm macOS release nameRun 'sw_vers -productVersionExtra' or check About This Mac to identify if the system is Sonoma (14.x) or Sequoia (15.x)Affected if Running Sonoma 14.0-14.8.3 or Sequoia 15.0-15.7.3 indicates a potentially vulnerable version
-
Verify security update statusCheck System Settings > General > Software Update for available updates, or run 'system_profiler SPSoftwareDataType' to see installed security updatesAffected if Security updates KB or build numbers corresponding to 14.8.4, 15.7.4, or later are NOT installed
The system is affected if it runs any macOS Sonoma version between 14.0 and 14.8.3, or any macOS Sequoia version between 15.0 and 15.7.3, without the corresponding security patches 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.415.7.4
Apply the macOS security updates: Sequoia 15.7.4, Sonoma 14.8.4, or Tahoe 26 (depending on macOS version). For managed endpoints, deploy via standard patch management processes.
macOS Sonoma 14.8.4+ or macOS Sequoia 15.7.4+ (or macOS Tahoe 26 if applicable)
- Back up important data before updating
- Go to System Settings > General > Software Update
- Click 'Check for Update' or enable automatic updates
- Download and install macOS Sonoma 14.8.4 (or later) or macOS Sequoia 15.7.4 (or later) depending on your current macOS version
- Restart the system 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-2025-46310 — 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-46310 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