CVE-2025-24093
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.3, macOS Ventura 13.7.3. An app may be able to access removable volumes without user consent.
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 permissions bypass vulnerability in macOS where an application could access removable volumes (USB drives, external hard drives, etc.) without obtaining user consent. The vulnerability was addressed by implementing additional permission restrictions in macOS Sequoia 15.4, Sonoma 14.7.3, and Ventura 13.7.3.
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.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 macOS versionClick Apple menu > About This Mac, or run 'sw_vers' in TerminalAffected if The version displayed is less than 13.7.3, or is 14.0 through 14.7.2 (including 14.0, 14.1, 14.2, 14.3, 14.4, 14.5, 14.6, 14.7, 14.7.1, or 14.7.2)
Your system is affected if it runs macOS Ventura older than 13.7.3, or macOS Sonoma between 14.0 and 14.7.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.3
Apply the appropriate macOS security update (15.4, 14.7.3, or 13.7.3) to affected systems to remediate the unauthorized removable volume access vulnerability.
macOS Ventura 13.7.3 / macOS Sonoma 14.7.3 / macOS Sequoia 15.4 (depending on your current major version)
- Determine your current macOS version by clicking the Apple menu > About This Mac
- For macOS Ventura users: Upgrade to macOS Ventura 13.7.3 or later via System Settings > General > Software Update
- For macOS Sonoma users: Upgrade to macOS Sonoma 14.7.3 or later via System Settings > General > Software Update
- For macOS Sequoia users: Upgrade to macOS Sequoia 15.4 or later via System Settings > General > Software Update
- After updating, verify the security update is installed by checking System Settings > General > About > System Version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24093 — 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-24093 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