CVE-2024-44240: Apple iOS and iPadOS · Processing a maliciously crafted font may result in the disclosure of process memory
Affects Apple iOS and iPadOSSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium · fixed in 17.7.1 : update Apple iOS and iPadOS when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 17.7.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation 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 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-44240, organizations should: 1) Immediately deploy the security updates released by Apple for all affected platforms, including iOS 17.7.1 and later, iPadOS 17.7.1 and later, macOS Sequoia 15.1 and later, macOS Sonoma 14.7.1 and later, macOS Ventura 13.7.1 and later, tvOS 18.1 and later, visionOS 2.1 and later, and watchOS 11.1 and later. 2) Implement strict email and document filtering to block or quarantine files containing suspicious or unknown font files, especially from untrusted sources. 3) Educate users about the risks of opening unsolicited attachments or links that may contain malicious fonts. 4) Employ endpoint detection and response (EDR) solutions capable of monitoring abnormal font processing or memory access patterns. 5) Restrict the use of third-party applications that handle fonts outside of trusted Apple ecosystem apps. 6) Maintain regular backups and incident response plans to quickly address any potential exploitation. These steps go beyond generic patching by focusing on reducing exposure to malicious font files and enhancing detection capabilities.
Description
The issue was addressed with improved checks. This issue is fixed in iOS 17.7.1 and iPadOS 17.7.1, iOS 18.1 and iPadOS 18.1, macOS Sequoia 15.1, macOS Sonoma 14.7.1, macOS Ventura 13.7.1, tvOS 18.1, visionOS 2.1, watchOS 11.1. Processing a maliciously crafted font may result in the disclosure of process memory.
References
- support.apple.com/en-us/121563 (opens in a new tab)
- support.apple.com/en-us/121564 (opens in a new tab)
- support.apple.com/en-us/121565 (opens in a new tab)
- support.apple.com/en-us/121566 (opens in a new tab)
- support.apple.com/en-us/121567 (opens in a new tab)
- support.apple.com/en-us/121568 (opens in a new tab)
- support.apple.com/en-us/121569 (opens in a new tab)
- support.apple.com/en-us/121570 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/16 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/15 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/13 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/12 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/11 (opens in a new tab)
- seclists.org/fulldisclosure/2024/Oct/10 (opens in a new tab)