Skip to main content
VulnerabilityPublished

CVE-2026-64750: Apple iOS and iPadOS · Processing a maliciously crafted image may result in memory corruption

Affects Apple iOS and iPadOSSource CVE Database V5

0

Not known to be exploited : upgrade to 27 or 26.7.2 soon.

Data as of 26 Oct 2026, 21:27 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Patch
Available – fixed in 27, 26.7.2, 15.8.2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Oct 2026

  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 26 Oct 2026.

What to do

Upgrade iOS and iPadOS to 27 or 26.7.2; macOS to 27, 26.7.2 or 15.8.2.

Affected software

ProductAffectedFixed in
AppleiOS and iPadOSAffected
  • <27
Fixed in
  • 27
AppleiOS and iPadOSAffected
  • <26.7.2
Fixed in
  • 26.7.2
ApplemacOSAffected
  • <27
Fixed in
  • 27
ApplemacOSAffected
  • <26.7.2
Fixed in
  • 26.7.2
ApplemacOSAffected
  • <15.8.2
Fixed in
  • 15.8.2

AI-suggested

Apply the official fixes by updating to iOS 26.7.2 or later, iPadOS 26.7.2 or later, or the specified macOS versions (15.8.2, 26.7.2, 27). These updates include improved bounds checking that resolves the vulnerability.

Description

A memory corruption vulnerability exists in Apple iOS and iPadOS due to an out-of-bounds write when processing maliciously crafted images. This issue is resolved by improved bounds checking and fixed in iOS 26.7.2, iOS 27, iPadOS 26.7.2, iPadOS 27, and macOS versions 15.8.2, 26.7.2, and 27. Processing a crafted image could lead to memory corruption, potentially impacting device stability or security.

References

Community reviews

Loading reviews…