CVE-2025-24248
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. An app may be able to enumerate devices that have signed into the user's Apple Account.
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 application to enumerate devices signed into the user's Apple Account. The issue stems from insufficient access controls that permitted apps to access Apple Account device information. It was patched in macOS Sequoia 15.4 with additional restrictions applied to this sensitive data.
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< 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
- Adjacent
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
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 System Settings > General > About to see the installed macOS version numberAffected if Version is below 15.4 (e.g., 15.3.x, 15.2.x, 15.1.x, 15.0.x, 14.x, 13.x, etc.)
-
Confirm macOS name and buildRun 'system_profiler SPSoftwareDataType' to get detailed OS information including build numberAffected if Build number corresponds to a version older than the security update released with macOS 15.4
-
Verify Apple Account statusCheck if a user Apple ID is signed into the system via System Settings > [your name] at the top of the sidebarAffected if An Apple Account is actively signed in on the Mac, making the device enumeration attack surface applicable
The system is affected if macOS version is below 15.4 and an Apple Account is signed in, allowing a malicious app to potentially enumerate the user's Apple Account devices.
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 · scoped15.4
Update affected systems to macOS Sequoia 15.4 or later. Organizations should deploy the Apple security update across managed Mac fleets and verify successful installation.
macOS Sequoia 15.4
- 1. Back up your Mac using Time Machine or another backup solution before updating.
- 2. Connect your Mac to power and a stable internet connection.
- 3. Open System Settings (or System Preferences on older macOS versions).
- 4. Navigate to General > Software Update.
- 5. Wait for macOS Sequoia 15.4 to appear as an available update.
- 6. Click 'Update Now' or 'Upgrade Now' to download and install the update.
- 7. Follow any on-screen prompts and allow the update to complete; your Mac may restart during the process.
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-24248 — 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-24248 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