Skip to main content
Mallory
HighVulnerability

CVE-2026-65346: Integer Overflow in Apple ImageIO Allowing Arbitrary Code Execution

Published Aug 17, 2026 · Updated 21 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS8.8High · v3.1
EPSS0.59%49th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Apple
IdentifiersCVE-2026-65346CWE-190 · Integer Overflow or Wraparound

CVE-2026-65346 is an integer overflow vulnerability in Apple's ImageIO image-processing framework. Processing a maliciously crafted image may trigger memory corruption and allow arbitrary code execution. The vulnerability affects multiple Apple operating systems, including iOS, iPadOS, macOS, tvOS, visionOS, and watchOS. Apple addressed the overflow through improved input validation. The specific vulnerable function and affected image formats have not been disclosed.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation may allow attacker-controlled code to execute in the context of the process handling the image, potentially compromising data and functionality accessible to that process. The vulnerability alone does not establish kernel-level execution, sandbox escape, or elevated privileges. In-the-wild exploitation was not confirmed at the time of the relevant security advisories.

Mitigation

If you can’t patch tonight, do this now.

Until updates are installed, avoid opening or processing images from untrusted sources and restrict exposure to untrusted image content where operationally feasible. Avoid relying solely on users not opening attachments, since applications may process images for previews or rendering. These measures reduce exposure but are not a confirmed complete workaround.

Remediation

Patch, then assume compromise.

Install the applicable Apple security update or a later supported release: iOS 26.6.1, iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, or watchOS 27. Legacy iPhone and iPad devices received corresponding fixes through iOS 18.7.10 and iPadOS 18.7.10. Deploy updates through Apple's standard software-update mechanisms and verify installation across managed devices, prioritizing systems that routinely process untrusted images.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIpadosoperating_system
AppleIphone Osoperating_system
AppleMacosoperating_system
FAQ

Frequently asked questions

Is CVE-2026-65346 exploited in the wild?
As of Oct 27, 2026, Mallory has no reports of CVE-2026-65346 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-65346?
As of Oct 27, 2026, Mallory has found no public exploit for CVE-2026-65346.
Is there a patch for CVE-2026-65346?
Install the applicable Apple security update or a later supported release: iOS 26.6.1, iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, or watchOS 27. Legacy iPhone and iPad devices received corresponding fixes through iOS 18.7.10 and iPadOS 18.7.10.
What products are affected by CVE-2026-65346?
Apple Ipados, Apple Macos, and Apple Iphone Os.
How severe is CVE-2026-65346?
CVE-2026-65346 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 0.59% (49th percentile) as of Oct 27, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.