VulnerabilityPublished 11 Dec 2024Updated 2 Apr 2026

CVE-2024-54531: Apple macOS · An app may be able to bypass kASLR

Affects Apple macOSSource CVE Database V5

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

Data as of 26 Oct 2026, 10:12 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 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 15.2

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
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: 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: 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 11 Dec 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-54531, organizations and users should promptly update all affected macOS systems to version Sequoia 15.2 or later, where the vulnerability is fixed. Beyond patching, organizations should enforce strict application control policies to limit the installation and execution of untrusted or unnecessary local applications that could exploit this vulnerability. Employing endpoint detection and response (EDR) solutions capable of monitoring for suspicious local privilege escalation attempts or unusual kernel memory access patterns can help detect exploitation attempts. Regularly auditing user privileges and minimizing the number of users with local access reduces the attack surface. Additionally, enabling system integrity protection (SIP) and other macOS security features can help prevent unauthorized kernel modifications. For environments where immediate patching is not feasible, isolating vulnerable systems and restricting local access can reduce risk. Finally, maintaining up-to-date threat intelligence feeds and monitoring for emerging exploit reports related to this CVE is recommended.

Description

The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.2. An app may be able to bypass kASLR.

Impact

The primary impact of CVE-2024-54531 is on the confidentiality of macOS kernel memory layout. By bypassing kASLR, an attacker can gain knowledge of kernel memory addresses, which significantly lowers the barrier for further kernel-level exploits, such as privilege escalation or arbitrary code execution. While this vulnerability alone does not grant elevated privileges or disrupt system availability, it is a critical enabler for more severe attacks. Organizations relying on macOS devices, especially those handling sensitive data or operating in high-security environments, face increased risk if the vulnerability is exploited in combination with other flaws. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future attacks. The vulnerability's local attack vector means that attackers must have some level of access to the system, which could be through compromised user accounts or malicious applications. Therefore, the impact is significant in environments where local threat actors or malicious insiders exist. The vulnerability could also be leveraged in targeted attacks against high-value macOS users or organizations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats