CVE-2024-40867VulnerabilityPublished 28 Oct 2024Updated 2 Apr 2026

CVE-2024-40867: Apple iOS and iPadOS · A remote attacker may be able to break out of Web Content sandbox

Affects Apple iOS and iPadOSSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.8High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: 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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 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-26.

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 iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-40867, organizations and users should immediately update all affected Apple devices to iOS and iPadOS version 18.1 or later, where the vulnerability is patched. Beyond patching, organizations should implement strict mobile device management policies that restrict installation of untrusted applications and enforce safe browsing practices. Employing network-level protections such as DNS filtering and web content filtering can help block access to malicious URLs that might exploit this vulnerability. User awareness training focused on phishing and social engineering risks is critical to reduce the likelihood of user interaction with malicious links. For high-security environments, consider disabling or restricting the use of custom URL schemes where feasible. Monitoring device behavior for anomalies indicative of sandbox escape or privilege escalation attempts can provide early detection of exploitation attempts. Finally, maintain an up-to-date inventory of Apple devices and ensure timely deployment of security updates as part of a robust patch management process.

Description

A custom URL scheme handling issue was addressed with improved input validation. This issue is fixed in iOS 18.1 and iPadOS 18.1. A remote attacker may be able to break out of Web Content sandbox.

Impact

The impact of CVE-2024-40867 is substantial for organizations and individuals relying on Apple iOS and iPadOS devices. Successful exploitation can lead to full device compromise, including unauthorized access to sensitive data, installation of persistent malware, and disruption of device functionality. This threatens confidentiality by exposing personal and corporate data, integrity by allowing unauthorized code execution and modification, and availability by potentially causing device instability or denial of service. Enterprises with mobile device management (MDM) deployments, especially those in regulated industries such as finance, healthcare, and government, face increased risk of data breaches and compliance violations. The vulnerability also undermines user trust in Apple’s security model. Given the ease of exploitation (no privileges required, only user interaction), attackers could leverage phishing or malicious websites to target users at scale. The lack of known exploits currently provides a window for proactive patching before widespread attacks emerge.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats