CVE-2025-24114
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.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3. 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 confidenceThis is a macOS permissions vulnerability that allowed a malicious or compromised application to modify protected parts of the file system, bypassing standard macOS sandboxing or restriction mechanisms. The fix adds additional restrictions to prevent unauthorized file system modifications.
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.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3CVSS 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.
-
Identify installed macOS versionOpen Terminal and run: sw_vers -productVersionAffected if The version output is less than 13.7.3, or between 14.0 and 14.7.2, or between 15.0 and 15.2
-
Check macOS build numberOpen Terminal and run: uname -a or system_profiler SPSoftwareDataTypeAffected if The OS version matches the affected ranges in step 1
-
Verify system update statusOpen System Settings > General > Software Update and check if updates are availableAffected if A security update is available but not installed, indicating the system is running an affected version
A system is affected if it is running macOS Ventura below 13.7.3, macOS Sonoma between 14.0 and 14.7.2, or macOS Sequoia between 15.0 and 15.2.
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.314.7.315.3
Apply the appropriate macOS security update: macOS Sequoia 15.3, macOS Sonoma 14.7.3, or macOS Ventura 13.7.3 depending on the installed OS version.
macOS Ventura 13.7.3 / macOS Sonoma 14.7.3 / macOS Sequoia 15.3 (depending on your current major version)
- Back up your Mac using Time Machine or another backup solution before proceeding with the update
- Check your current macOS version by clicking the Apple menu > About This Mac
- Determine which macOS major version you are running (Ventura 13.x, Sonoma 14.x, or Sequoia 15.x)
- Open System Settings (or System Preferences on older macOS) > General > Software Update
- Allow the system to check for available updates
- If an update is available, click Download and Install
- For macOS Ventura 13.x users: Install macOS Ventura 13.7.3 or later
- For macOS Sonoma 14.x users: Install macOS Sonoma 14.7.3 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24114 — 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-24114 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