CVE-2025-24101
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 redaction of sensitive information. This issue is fixed in macOS Sequoia 15.3. An app may be able to access user-sensitive data.
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 confidenceA vulnerability in macOS allowed an application to access user-sensitive data that should have been redacted. The fix in macOS Sequoia 15.3 implemented improved redaction of sensitive information, preventing unauthorized access to private user data through the affected code path.
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.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 macOS version via System SettingsOpen System Settings, then go to General > About. Read the macOS version number displayed next to 'macOS'.Affected if The version shown is less than 15.3 (for example, 15.2, 14.x, 13.x, etc.)
-
Check macOS version via terminalOpen Terminal and run: sw_vers -productVersionAffected if The output shows a version lower than 15.3 (for example, 15.2.x, 14.x.x, 13.x.x)
-
Confirm the build number if neededIn System Settings > General > About, note the Build number. Compare it to builds included in macOS 15.3 (such as 24D5024d or later).Affected if The build number corresponds to a pre-15.3 release
You are affected if your macOS version is any release prior to 15.3, as the vulnerability exists in the older redaction mechanism that was fixed in the 15.3 update.
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.3
Update to macOS Sequoia 15.3 or later to apply the improved redaction of sensitive information.
macOS Sequoia 15.3
- Back up your Mac using Time Machine or another backup method before performing any system update
- Connect your Mac to power to ensure the update is not interrupted
- Open System Settings (or System Preferences on older macOS versions)
- Click on General in the sidebar
- Click on Software Update
- Allow macOS to check for updates - if macOS Sequoia 15.3 is available, it will appear in the list
- Click Update Now or Install Now next to macOS Sequoia 15.3
- Follow the on-screen instructions and wait for the update to complete
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-24101 — 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-24101 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