VulnerabilityPublished 16 Sep 2024Updated 2 Apr 2026

CVE-2024-44133: Apple macOS · On MDM managed devices, an app may be able to bypass certain Privacy preferences

Affects Apple macOSSource CVE Database V5

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.5Medium

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

EPSS: 7.7% chance of exploitation in 30 days – higher than 94% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: High
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 or the CVSS exploit maturity 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-44133, organizations should promptly update all MDM-managed macOS devices to macOS Sequoia 15 or later, where the vulnerable code has been removed. Beyond patching, administrators should audit and tighten MDM privacy configurations to minimize app permissions and restrict installation of untrusted applications. Employing application allowlisting and endpoint detection solutions can help identify suspicious app behavior attempting to bypass privacy controls. Regularly reviewing MDM policy enforcement logs can detect anomalies indicative of exploitation attempts. Additionally, limiting local user privileges and enforcing strong access controls reduces the risk of initial compromise needed to exploit this vulnerability. Organizations should also educate users about the risks of installing unauthorized software on managed devices. For environments where immediate patching is not feasible, temporarily restricting app installation and tightening privacy settings manually can reduce exposure.

Description

This issue was addressed by removing the vulnerable code. This issue is fixed in macOS Sequoia 15. On MDM managed devices, an app may be able to bypass certain Privacy preferences.

Impact

The primary impact of CVE-2024-44133 is on the integrity of macOS systems managed via MDM. By bypassing Privacy preferences, malicious or compromised applications can perform unauthorized actions that could alter system settings, manipulate user data, or interfere with security controls. This undermines the trust model of MDM-managed devices, where administrators rely on privacy restrictions to enforce security policies. Although confidentiality is not directly impacted, the ability to bypass privacy controls can facilitate further attacks, such as privilege escalation or persistence mechanisms. The vulnerability requires local access, so initial compromise or insider threat scenarios are relevant. Organizations worldwide that deploy Apple macOS devices under MDM management—especially enterprises, educational institutions, and government agencies—face increased risk of targeted attacks exploiting this flaw. Failure to patch could lead to unauthorized system modifications, data integrity issues, and potential lateral movement within networks.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats