CVE-2025-24267
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.4, macOS Sonoma 14.7.5, macOS Ventura 13.7.5. An 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 local privilege escalation vulnerability in macOS where an application can bypass permission restrictions to gain root privileges. The fix was implemented through additional restrictions, likely addressing an authorization or sandboxing bypass in the system's permission model.
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>= 13.0, < 13.7.5>= 14.0, < 14.7.5>= 15.0, < 15.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
- 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.
-
Identify installed macOS versionRun 'sw_vers -productVersion' in Terminal to display the exact macOS version numberAffected if The version displayed is 13.0 to 13.7.4, 14.0 to 14.7.4, or 15.0 to 15.3.x (falls within vulnerable ranges)
-
Confirm macOS release nameRun 'sw_vers -productName' to verify whether the system is running Ventura (13.x), Sonoma (14.x), or Sequoia (15.x)Affected if The product is Ventura, Sonoma, or Sequoia and the version from step 1 is within the vulnerable range for that release
-
Check if security updates are installedView System Settings > General > Software Update to see installed updates, or run 'system_profiler SPSoftwareDataType' and look for recent security update entriesAffected if No security update corresponding to 13.7.5, 14.7.5, or 15.4 is listed as installed
The system is affected if it runs macOS Ventura 13.0-13.7.4, Sonoma 14.0-14.7.4, or Sequoia 15.0-15.3.x and has not received the security update for CVE-2025-24267.
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 · scoped13.7.514.7.515.4
Apply the macOS security updates: upgrade to macOS Sequoia 15.4, macOS Sonoma 14.7.5, or macOS Ventura 13.7.5 as appropriate for your environment.
macOS Ventura 13.7.5 / macOS Sonoma 14.7.5 / macOS Sequoia 15.4 (depending on your current major version)
- Open System Settings (or System Preferences on older macOS)
- Click on General in the sidebar
- Click on Software Update
- Allow the system to check for updates
- If macOS Ventura 13.7.5, Sonoma 14.7.5, or Sequoia 15.4 is available, click Update Now or Download & Install
- Follow the on-screen prompts to complete the update
- Restart the Mac when prompted to ensure the update is fully applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24267 — 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-24267 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