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

CVE-2024-44130: Apple macOS · An app with root privileges may be able to access private information

Affects Apple macOSSource CVE Database V5

Not known to be exploited · CVSS 4.4 Medium.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

4.4Medium

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:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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 26 Oct 2026.

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-2024-44130, organizations should promptly upgrade all affected macOS systems to macOS Sequoia 15, where the vulnerability is fixed with enhanced data protection. Review and audit all applications and services running with root privileges to ensure they adhere to the principle of least privilege and do not unnecessarily require elevated access. Implement strict access controls and monitoring on systems to detect and prevent unauthorized elevation to root privileges. Employ endpoint detection and response (EDR) tools capable of identifying suspicious behavior by root-level processes accessing sensitive data. Consider deploying application whitelisting and integrity verification to prevent unauthorized or malicious root-level applications from executing. Regularly back up sensitive data and maintain incident response plans to address potential data exposure events. Educate system administrators on the risks of running untrusted code with root privileges and enforce policies to minimize such practices. Finally, stay informed on Apple security advisories for any further updates or related vulnerabilities.

Description

This issue was addressed with improved data protection. This issue is fixed in macOS Sequoia 15. An app with root privileges may be able to access private information.

Impact

The primary impact of CVE-2024-44130 is the unauthorized disclosure of private information on macOS systems when an application with root privileges exploits the vulnerability. This can lead to sensitive data exposure, including user credentials, personal files, or system secrets, potentially facilitating further attacks or privacy violations. Since exploitation requires root access, the vulnerability mainly escalates the damage an attacker with existing high privileges can cause, rather than enabling initial compromise. Organizations relying on macOS for critical operations, especially those running custom or third-party software with root privileges, face increased risk of data leakage. The confidentiality breach could undermine trust, lead to regulatory compliance issues, and expose intellectual property or personal data. However, the lack of impact on integrity or availability limits the scope of damage to data exposure rather than system disruption or corruption. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially in environments where attackers may gain root access through other means.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats