CVE-2025-24092
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 with improved data protection. This issue is fixed in macOS Sequoia 15.3, macOS Sonoma 14.7.3. An app may be able to read sensitive location information.
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 · high confidenceA vulnerability in macOS allowed an application to read sensitive location information due to insufficient data protection controls. The issue was addressed in macOS Sequoia 15.3 and macOS Sonoma 14.7.3 through improved data protection mechanisms.
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.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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Check installed macOS versionRun `sw_vers -productVersion` in Terminal or go to System Settings > About to view the macOS versionAffected if Version is earlier than 14.7.3, or is 15.0, 15.1, or 15.2
-
Confirm macOS release nameRun `sw_vers -productVersionExtra` or check the macOS name in System Settings > About (such as Sonoma or Sequoia)Affected if Running macOS Sonoma below 14.7.3 or macOS Sequoia below 15.3
-
Verify if location services are accessibleThis check is implicit - the vulnerability allows ANY application to read location data if the system is vulnerable, regardless of user permissionsAffected if System is running an affected macOS version as identified above
A system is affected if it is running any version of macOS Sonoma before 14.7.3 or macOS Sequoia before 15.3.
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.7.315.3
Update affected Mac systems to macOS Sequoia 15.3, macOS Sonoma 14.7.3, or later versions to apply the data protection fixes.
macOS Sonoma 14.7.3 or macOS Sequoia 15.3
- Click the Apple menu and select 'About This Mac' to check your current macOS version
- If running macOS Sonoma (14.x), update to version 14.7.3 or later
- If running macOS Sequoia (15.0-15.2), update to version 15.3 or later
- To update: Open System Settings > General > Software Update and install available updates
- Alternatively, download the appropriate macOS installer from the Mac App Store or Apple website and reinstall the OS
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-24092 — 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-24092 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