macOSOperating system · Apple

CVE-2025-24146

CRITICAL · 9.8 CVSS v3.1 Published 2025-01-27
Fix available
A fix is available. Upgrade to 13.7.3 / 14.7.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
This issue was addressed with improved redaction of sensitive information. This issue is fixed in macOS Sequoia 15.3, macOS Sonoma 14.7.3, macOS Ventura 13.7.3. Deleting a conversation in Messages may expose user contact information in system logging.

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 confidence

Deleting a conversation in Messages on macOS may expose user contact information (phone numbers or Apple IDs) in system logs due to insufficient redaction of sensitive data during the deletion operation.

MitigationUpdate macOS to version 15.3 (Sequoia), 14.7.3 (Sonoma), or 13.7.3 (Ventura) which contains improved redaction of sensitive information in logging.

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
macOSOperating system
Affected:< 13.7.3>= 14.0, < 14.7.3>= 15.0, < 15.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check your macOS version
    Go to Apple menu > About This Mac to view the installed macOS version number
    Affected if The version is earlier than 13.7.3, or falls between 14.0 and 14.7.2, or falls between 15.0 and 15.2 (these ranges contain the vulnerability)
  2. Determine if you use the Messages app
    Open the Messages app and check if any conversations exist in your message history
    Affected if You have used Messages to send or receive messages, meaning the app has processed conversation data that may have been logged
  3. Inspect system logs for exposed contact information
    Use Console.app or the log command-line tool to search system logs for entries containing phone numbers or Apple IDs from your contacts that may have been logged during conversation deletion operations
    Affected if Logs contain unredacted phone numbers or Apple IDs that should have been masked during deletion operations

You are affected if your macOS version is below 15.3 (or below 14.7.3 on Sonoma, or below 13.7.3 on Ventura) AND you have used the Messages app, as the vulnerability allows contact information to appear in logs during conversation deletion.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 13.7.3 / 14.7.3 / 15.3 or later
Fixed in 13.7.314.7.315.3
Interim mitigation

Update macOS to version 15.3 (Sequoia), 14.7.3 (Sonoma), or 13.7.3 (Ventura) which contains improved redaction of sensitive information in logging.

Recommended fix High confidence

macOS 13.7.3 (Ventura), macOS 14.7.3 (Sonoma), or macOS 15.3 (Sequoia) depending on your current major version

  1. 1. Check your current macOS version by clicking the Apple menu and selecting 'About This Mac'
  2. 2. If running macOS Ventura 13.x: Upgrade to macOS 13.7.3 via System Settings > Software Update
  3. 3. If running macOS Sonoma 14.x: Upgrade to macOS 14.7.3 via System Settings > Software Update
  4. 4. If running macOS Sequoia 15.0-15.2: Upgrade to macOS 15.3 via System Settings > Software Update
  5. 5. After upgrading, verify the update was applied in About This Mac

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in macOS Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24146 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24146 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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