CVE-2025-24101VulnerabilityPublished 27 Jan 2025Updated 2 Apr 2026

CVE-2025-24101: Apple macOS · An app may be able to access user-sensitive data

Affects Apple macOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium · fixed in 15.3 : update Apple macOS when convenient.

Data as of 26 Oct 2026, 06:15 UTC

CVSS 3.1 base score

5.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.3

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apple macOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-24101, organizations should prioritize updating all macOS devices to version Sequoia 15.3 or later, where the vulnerability has been addressed through improved data redaction. Beyond patching, organizations should implement application control policies to restrict the installation and execution of untrusted or unsigned applications, reducing the risk of malicious apps exploiting this flaw. User education is critical to minimize risky behaviors such as running unknown software or clicking on suspicious links that could trigger exploitation. Employ endpoint detection and response (EDR) solutions capable of monitoring for anomalous application behaviors that may indicate attempts to access sensitive data improperly. Additionally, enforce the principle of least privilege for user accounts and applications to limit the potential impact of any compromise. Regularly audit and monitor sensitive data access logs to detect unusual access patterns. Finally, maintain an up-to-date inventory of macOS devices and ensure timely deployment of security updates to reduce exposure windows.

Description

This 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.

Impact

The primary impact of CVE-2025-24101 is the unauthorized disclosure of sensitive user data on macOS devices. This can lead to privacy violations, leakage of personally identifiable information (PII), corporate secrets, or other confidential data. Organizations relying on macOS for business operations, especially those handling sensitive or regulated data, may face compliance risks and reputational damage if this vulnerability is exploited. Although the vulnerability does not affect system integrity or availability, the exposure of sensitive data can facilitate further attacks such as social engineering, identity theft, or targeted intrusions. The requirement for user interaction limits the ease of exploitation but does not eliminate risk, as users may inadvertently run malicious applications. The absence of known exploits in the wild suggests limited current threat activity, but the medium severity score indicates that attackers could develop effective exploits. Enterprises with large macOS deployments, including government, finance, healthcare, and technology sectors, are particularly at risk due to the value of the data potentially exposed.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 00:28 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats