CVE-2024-40824: Apple iOS and iPadOS · An app may be able to bypass Privacy preferences
Affects Apple iOS and iPadOSSource CVE Database V5
Not known to be exploited · CVSS 7.7 High · fixed in 17.6 : patch Apple iOS and iPadOS soon.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.6
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Jul 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Apple iOS and iPadOS | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-40824, organizations and users should promptly update all affected Apple devices to iOS 17.6, iPadOS 17.6, or later versions, as well as macOS Sonoma 14.6, tvOS 17.6, and watchOS 10.6 where applicable. Beyond patching, organizations should enforce strict app vetting and only allow apps from trusted sources such as the official Apple App Store. Implement Mobile Device Management (MDM) solutions to monitor and restrict app installations and permissions. Regularly audit installed apps for suspicious behavior or excessive permission requests. Employ endpoint security solutions capable of detecting anomalous app activities related to privacy bypass attempts. Educate users about the risks of installing untrusted apps and the importance of applying system updates promptly. For high-security environments, consider additional controls such as disabling local device access for unauthorized personnel and using hardware-based security features like Secure Enclave. Monitoring device logs for unusual access patterns to privacy-sensitive resources can also help detect exploitation attempts early. Finally, maintain an incident response plan that includes steps for addressing potential privacy breaches on Apple devices.
Description
This issue was addressed through improved state management. This issue is fixed in iOS 17.6 and iPadOS 17.6, macOS Sonoma 14.6, tvOS 17.6, watchOS 10.6. An app may be able to bypass Privacy preferences.
References
- support.apple.com/en-us/120909 (opens in a new tab)
- support.apple.com/en-us/120911 (opens in a new tab)
- support.apple.com/en-us/120914 (opens in a new tab)
- support.apple.com/en-us/120916 (opens in a new tab)
- support.apple.com/en-us/HT214117 (opens in a new tab)
- support.apple.com/en-us/HT214124 (opens in a new tab)
- support.apple.com/en-us/HT214119 (opens in a new tab)
- support.apple.com/en-us/HT214122 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/16 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/21 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/22 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Jul/18 (opens in a new tab)
- support.apple.com/kb/HT214124 (opens in a new tab)
- support.apple.com/kb/HT214122 (opens in a new tab)
- support.apple.com/kb/HT214119 (opens in a new tab)
- support.apple.com/kb/HT214117 (opens in a new tab)