CVERadar
CRITICAL · CVSS 3.1 9.8Public PoCEPSS 2.29% (p83)Threat level 54

CVE-2025-24204: CVE-2025-24204: The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4. A…

apple · macos · NVD published 2025-04-01 · posted 2025-08-15 · last modified 2026-06-17

What it is

The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4. An app may be able to access protected user data.

WeaknessCWE-200
CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
ATT&CK tacticsCollection

Exploitation evidence

First exploit evidence seen: 2025-08-15 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

2 public repositories from 2 accounts, first seen 2025-08-15. Most starred: 34306/decrypted (157 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • apple macos: upgrade to 15.4 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

  • M1057 Data Loss Prevention (for T1005) : Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.

Detection Generic guidance

  • Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources