VulnerabilityPublished 11 Dec 2024Updated 2 Apr 2026

CVE-2024-54514: Apple iOS and iPadOS · An app may be able to break out of its sandbox

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 8.2 High · fixed in 18.2 : patch Apple iOS and iPadOS soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.2High

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

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

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

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Changed
Confidentiality: High
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: 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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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: 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 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 iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-54514 effectively, organizations should: 1) Immediately deploy the official patches released by Apple for iOS 18.2, iPadOS 18.2, macOS Sequoia 15.2, Sonoma 14.7.2, Ventura 13.7.2, tvOS 18.2, and watchOS 11.2 to ensure the vulnerability is remediated. 2) Enforce strict app vetting policies and restrict installation of apps from untrusted sources to reduce the risk of malicious apps exploiting the vulnerability. 3) Implement mobile device management (MDM) solutions to control app permissions and monitor for anomalous app behavior indicative of sandbox escape attempts. 4) Educate users about the risks of interacting with untrusted apps or links that could trigger exploitation. 5) Monitor device logs and security telemetry for signs of sandbox breakout attempts or privilege escalation activities. 6) Consider deploying endpoint detection and response (EDR) tools capable of detecting unusual process behaviors on Apple devices. 7) Maintain an inventory of Apple devices and ensure all are updated promptly, prioritizing those in sensitive roles or handling critical data. 8) Coordinate with Apple support and security advisories to stay informed about any emerging exploit reports or additional mitigations.

Description

The issue was addressed with improved checks. This issue is fixed in iOS 18.2 and iPadOS 18.2, macOS Sequoia 15.2, macOS Sonoma 14.7.2, macOS Ventura 13.7.2, tvOS 18.2, watchOS 11.2. An app may be able to break out of its sandbox.

Impact

The potential impact of CVE-2024-54514 is substantial for organizations worldwide that rely on Apple devices for daily operations, communications, and sensitive data handling. A successful sandbox escape could allow a malicious app to access protected system resources, user data, or other apps’ data, leading to confidentiality breaches and integrity violations. This could facilitate further attacks such as privilege escalation, installation of persistent malware, or unauthorized data exfiltration. The vulnerability does not affect availability directly but undermines trust in the device’s security model. Enterprises in sectors like finance, healthcare, government, and critical infrastructure that use iOS or iPadOS devices for secure communications or data processing are at heightened risk. The requirement for user interaction means social engineering or malicious app distribution vectors could be exploited. Although no known exploits exist yet, the high severity and broad platform impact necessitate urgent mitigation to avoid potential targeted attacks or widespread exploitation once proof-of-concept code becomes available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats