Skip to main content
CVE-2024-44205VulnerabilityPublished Updated

CVE-2024-44205: Apple iOS and iPadOS · A sandboxed app may be able to access sensitive user data in system logs

Affects Apple iOS and iPadOSSource CVE Database V5

0

Not known to be exploited · CVSS 5.5 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
Apple iOS and iPadOSAffected
  • =0
Fixed in–

AI-suggested

Apple has released official fixes for this vulnerability in iOS 16.7.9, iPadOS 16.7.9, iOS 17.6, and iPadOS 17.6. Users and administrators should update affected devices to these versions or later to remediate the issue. Since this is not a cloud service, patching the device OS is required. There are no known exploits in the wild, but timely updating is recommended to prevent potential privacy exposure.

Description

CVE-2024-44205 is a privacy vulnerability in Apple iOS and iPadOS where a sandboxed app may access sensitive user data in system logs. Apple addressed this issue by improving private data redaction in log entries. The vulnerability affects versions prior to iOS 16.7.9, iPadOS 16.7.9, iOS 17.6, and iPadOS 17.6. The issue is fixed in these versions as well as in macOS updates.

References

Community reviews

Loading reviews…