CVE-2025-24142
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 privacy issue was addressed with improved private data redaction for log entries. This issue is fixed in macOS Sequoia 15.5, macOS Sonoma 14.7.6, macOS Ventura 13.7.6. An app may be able to access sensitive user 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 privacy vulnerability in macOS allowed applications to access sensitive user data due to insufficient private data redaction in system log entries. The issue was addressed with improved redaction logic for log 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< 13.7.6>= 14.0, < 14.7.6>= 15.0, < 15.5CVSS 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.
-
Determine installed macOS versionClick Apple menu > About This Mac to view the macOS version number (e.g., 14.4, 15.3, etc.)Affected if Version is in an affected range: below 13.7.6, between 14.0-14.7.5, or between 15.0-15.4
-
Confirm full version numberOpen Terminal and run: sw_vers -productVersion to get the exact version (e.g., 14.7.5, 15.4)Affected if The version falls within any of the vulnerable ranges listed above
-
Verify build number for additional contextOpen Terminal and run: uname -a or system_profiler SPSoftwareDataType to see build detailsAffected if Build corresponds to an affected macOS release (Ventura < 13.7.6, Sonoma < 14.7.6, or Sequoia < 15.5)
You are affected if your macOS version is any release prior to 13.7.6, 14.7.6, or 15.5 - the vulnerability exists in those unpatched versions where log redaction is insufficient.
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.614.7.615.5
Apply the appropriate macOS security update (Sequoia 15.5, Sonoma 14.7.6, or Ventura 13.7.6) to address the improper private data redaction in log entries.
macOS 13.7.6 (Ventura), macOS 14.7.6 (Sonoma), or macOS 15.5 (Sequoia) depending on your current major version
- Check the current macOS version by clicking the Apple menu > About This Mac
- Back up your Mac using Time Machine or another backup method before updating
- Open System Settings (System Preferences on older macOS) > General > Software Update
- Click Check for Update and wait for macOS to find available updates
- Select the security update (macOS 13.7.6, 14.7.6, or 15.5 depending on your current version)
- Click Install Now or Install Update and enter your administrator password when prompted
- Restart your Mac when prompted to complete the installation
- After restart, verify the update by checking About This Mac shows the patched version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24142 — 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-24142 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