CVE-2024-44125VulnerabilityPublished 16 Sep 2024Updated 2 Apr 2026

CVE-2024-44125: Apple macOS · A malicious application may be able to leak sensitive user information

Affects Apple macOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 25 Oct 2026, 19:02 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.

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 16 Sep 2024
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

Organizations and users should promptly update macOS systems to Sequoia 15 or Sonoma 14.7 or later, where the vulnerability is fixed. Beyond patching, implement application whitelisting to restrict installation and execution of untrusted or unknown applications, reducing the chance of malicious apps running. Employ endpoint protection solutions capable of detecting suspicious behaviors associated with data leakage attempts. Educate users about the risks of running unverified applications and the importance of cautious interaction with software prompts. Use macOS security features such as Gatekeeper and System Integrity Protection (SIP) to limit unauthorized app capabilities. Regularly audit installed applications and remove any that are unnecessary or untrusted. Monitor system logs for unusual access patterns to sensitive information. For organizations, enforce strict policies on software installation and use mobile device management (MDM) tools to control macOS device configurations and updates.

Description

The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15, macOS Sonoma 14.7. A malicious application may be able to leak sensitive user information.

Impact

The primary impact of CVE-2024-44125 is the unauthorized disclosure of sensitive user information, which can lead to privacy violations, identity theft, or further targeted attacks such as phishing or social engineering. Because the vulnerability does not require elevated privileges, any malicious app that a user runs could potentially exploit this flaw, increasing the attack surface. Organizations relying on macOS devices for sensitive operations or handling confidential data are at risk of data leakage, which could result in regulatory compliance issues and reputational damage. Although the vulnerability does not affect system integrity or availability, the confidentiality breach alone can have serious consequences, especially in sectors like finance, healthcare, and government. The requirement for user interaction limits large-scale automated exploitation but does not eliminate risk, as social engineering techniques can be effective. The absence of known exploits in the wild reduces immediate risk but does not preclude future exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Apr 2026, 23:42 UTC

Technical details

References

Community reviews

Related threats