Apple’s iOS 26.6 and iPadOS 26.6 update closes 87 distinct CVEs across 78 security entries for supported iPhones and iPads, and the practical advice is straightforward: install it now. Apple released the update on July 27, 2026, for iPhone 11 and later, while the company’s security bulletin covers flaws ranging from image parsing and browser isolation to kernel-privileged code execution.
The distinction between 78 entries and 87 CVE identifiers is more than bookkeeping. Several Apple bulletin entries cover multiple CVEs, which explains why reporting has alternated between “more than 75 fixes,” “78 vulnerabilities,” and “87 vulnerabilities.” Apple’s own advisory is the primary record; 9to5Mac separately counted 78 entries mapped to 87 unique CVEs, while MacRumors characterized the set as almost 90 security vulnerabilities. All three descriptions point to the same patch set.
Apple has not said that any iOS 26.6 flaw is being exploited in the wild. That is a meaningful difference from an emergency zero-day release. But the update fixes bugs with dangerous post-compromise effects, and public disclosure gives researchers and attackers a clearer map of what older devices are missing.
The most serious issues are concentrated in components that have broad privileges or process untrusted content.
CVE-2026-43818 in ImageIO is the clearest example of a remotely reachable class of risk. Apple says that processing a maliciously crafted image can lead to arbitrary code execution, caused by an integer-overflow flaw. ImageIO is used broadly across Apple platforms, including when apps render images and previews, so it deserves priority attention.
The supplied reporting calls this a zero-click vulnerability. The public Apple advisory does not establish that. Apple confirms that a crafted image must be processed; it does not identify a delivery route, say that Messages or notifications will automatically trigger the vulnerable path, or document an exploit chain requiring no user action. That does not make the issue harmless, but it means “zero-click” is an inference, not a confirmed attribute of CVE-2026-43818.
CVE-2026-64747 in AVEVideoEncoder has a more severe stated result: a malicious app may be able to execute arbitrary code with kernel privileges. Apple attributes the flaw to a buffer overflow fixed through improved size validation. Kernel-level code execution is especially concerning because it can undermine operating-system isolation rather than merely crash a single application.
Yet this is also where operational context matters. Apple’s stated attack prerequisite is an app, not a web page, incoming video, or unauthenticated network request. For organizations managing iPhones, that shifts the immediate exposure toward devices where untrusted applications can be installed, sideloaded under enterprise provisioning, or deployed through weak internal controls. Updating remains the remedy, but the bulletin does not support presenting this as an unauthenticated remote takeover bug.
CVE-2026-43723 in MediaRemote may let an app gain root privileges through improper path handling. CVE-2026-43813 in CloudAttestation may allow a maliciously crafted app to bypass code-signing enforcement. Both should be viewed as escalation components: a bad app that has already reached the device could use them to reach beyond normal application privileges or evade an intended code-integrity boundary.
The submitted report also listed CVE-2026-64767 in “afpfs” as an unauthenticated remote kernel-memory-corruption flaw. That identifier does not appear in Apple’s iOS 26.6 security advisory. It should not be included in an iOS 26.6 risk assessment unless Apple or another primary CVE record links it to the update.
CVE-2026-64740 affects Game Center. Apple describes a directory-path parsing issue that could allow a malicious app to escape its sandbox. CVE-2026-28973 affects libc, the system’s core C library, and fixes an integer overflow with the same potential outcome.
These bugs matter because app sandbox escapes are rarely the beginning of an attack. They are the middle. An attacker still needs a foothold, such as a malicious or compromised app, but escaping the sandbox can turn a confined compromise into access to data and services that should have been unavailable.
For IT administrators, the immediate inventory question is not merely whether the fleet contains iPhones. It is whether the organization’s mobile-device-management policies permit delayed OS updates, allow developer mode where it is unnecessary, or tolerate unreviewed enterprise-distributed apps. The iOS 26.6 bulletin makes the cost of those exceptions clearer.
Apple also patched an Accessibility issue affecting iPhone Mirroring that could expose sensitive information to someone with physical access. That does not have the same remote attack profile, but it is relevant in shared workspaces, repair depots, travel scenarios, and environments where an unlocked Mac may be paired with a nearby iPhone.
CVE-2026-64713 addresses history sniffing: a website could determine whether a user had visited a particular link. CVE-2026-64728 could let malicious web content violate an iframe sandboxing policy, while CVE-2026-64730 addresses UI spoofing through framed malicious content. CVE-2026-43821 affects WebKit access controls and could allow an app to read files outside its sandbox.
The research credits in Apple’s bulletin have attracted understandable attention. Apple credits Milad Nasr and Nicholas Carlini “with Claude, Anthropic” for CVE-2026-64757, a WebKit memory-corruption issue that could crash Safari when it processes malicious web content. Apple’s entry does not say Claude independently discovered the bug, nor does it establish an automated exploitation capability. It records the researchers’ attribution in the advisory.
Similarly, Apple credits contributors “using GLM from Z.AI” on CVE-2026-64783, a WebKit use-after-free issue that could crash Safari. These credits show AI-assisted security work appearing in Apple’s public acknowledgments. They do not prove the broader claim that AI has caused vulnerability discovery to “skyrocket,” and Apple has published no metric in this release connecting AI tools to a July total of 210 CVEs.
The same caution applies to claims about Codex. Apple’s iOS 26.6 advisory includes Codex Security in its additional-recognition section for WebKit Canvas, but additional recognition is not a CVE assignment and does not identify a specific watchOS discovery. Apple’s security documentation credits assistance; it does not provide a detailed methodology for how each tool or researcher contributed.
Apple’s iOS 26.6 advisory lists CVE-2026-3783 and CVE-2026-3784 under curl. The impact is that authentication credentials may be sent to a server on another origin. Apple describes it as an open-source vulnerability for which the CVE was assigned by a third party.
A proof of concept is not evidence of widespread exploitation, and neither Apple nor MacRumors has reported active attacks against iOS 26.6’s patched vulnerabilities. Still, it narrows the usual gap between publication and practical testing. The combined release covered iOS and iPadOS 26.6, macOS Tahoe 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, watchOS 26.6, tvOS 26.6, visionOS 26.6, and Safari 26.6; leaving any of those behind creates inconsistent protection for users who move data among Apple devices.
The update does not, however, substantiate reports of an enabled anti-snatching lock feature, a universally documented download size, or a guaranteed five-to-eight-minute installation window. Those vary by device, storage state, network conditions, and Apple’s staged delivery. Apple’s published release information emphasizes security fixes and Spotlight preparation, not a long list of new iPhone features.
Install iOS 26.6 through Settings > General > Software Update, then verify companion devices are patched to their respective July releases. For a Windows-managed environment, that means checking iPhones and iPads through MDM compliance reporting rather than assuming that an employee’s iPhone update also protected their Apple Watch, Mac, or Safari installation.
The key consequence is simple: iOS 26.6 does not appear to be a live zero-day emergency, but it patches flaws that can provide arbitrary code execution, kernel-level execution, root privilege, code-signing bypass, browser privacy leakage, and sandbox escape. On August 2, 2026, an iPhone still running a pre-26.6 build is missing all 87 CVE fixes Apple has now made public.
Apple has not said that any iOS 26.6 flaw is being exploited in the wild. That is a meaningful difference from an emergency zero-day release. But the update fixes bugs with dangerous post-compromise effects, and public disclosure gives researchers and attackers a clearer map of what older devices are missing.
ImageIO, AVEVideoEncoder, and MediaRemote are the urgent fixes
The most serious issues are concentrated in components that have broad privileges or process untrusted content.CVE-2026-43818 in ImageIO is the clearest example of a remotely reachable class of risk. Apple says that processing a maliciously crafted image can lead to arbitrary code execution, caused by an integer-overflow flaw. ImageIO is used broadly across Apple platforms, including when apps render images and previews, so it deserves priority attention.
The supplied reporting calls this a zero-click vulnerability. The public Apple advisory does not establish that. Apple confirms that a crafted image must be processed; it does not identify a delivery route, say that Messages or notifications will automatically trigger the vulnerable path, or document an exploit chain requiring no user action. That does not make the issue harmless, but it means “zero-click” is an inference, not a confirmed attribute of CVE-2026-43818.
CVE-2026-64747 in AVEVideoEncoder has a more severe stated result: a malicious app may be able to execute arbitrary code with kernel privileges. Apple attributes the flaw to a buffer overflow fixed through improved size validation. Kernel-level code execution is especially concerning because it can undermine operating-system isolation rather than merely crash a single application.
Yet this is also where operational context matters. Apple’s stated attack prerequisite is an app, not a web page, incoming video, or unauthenticated network request. For organizations managing iPhones, that shifts the immediate exposure toward devices where untrusted applications can be installed, sideloaded under enterprise provisioning, or deployed through weak internal controls. Updating remains the remedy, but the bulletin does not support presenting this as an unauthenticated remote takeover bug.
CVE-2026-43723 in MediaRemote may let an app gain root privileges through improper path handling. CVE-2026-43813 in CloudAttestation may allow a maliciously crafted app to bypass code-signing enforcement. Both should be viewed as escalation components: a bad app that has already reached the device could use them to reach beyond normal application privileges or evade an intended code-integrity boundary.
The submitted report also listed CVE-2026-64767 in “afpfs” as an unauthenticated remote kernel-memory-corruption flaw. That identifier does not appear in Apple’s iOS 26.6 security advisory. It should not be included in an iOS 26.6 risk assessment unless Apple or another primary CVE record links it to the update.
Two sandbox escapes change the value of a malicious app
iOS security relies heavily on sandboxing: applications are supposed to remain fenced off from one another and from sensitive operating-system resources. iOS 26.6 fixes two flaws that Apple explicitly says could let a malicious app break out of that boundary.CVE-2026-64740 affects Game Center. Apple describes a directory-path parsing issue that could allow a malicious app to escape its sandbox. CVE-2026-28973 affects libc, the system’s core C library, and fixes an integer overflow with the same potential outcome.
These bugs matter because app sandbox escapes are rarely the beginning of an attack. They are the middle. An attacker still needs a foothold, such as a malicious or compromised app, but escaping the sandbox can turn a confined compromise into access to data and services that should have been unavailable.
For IT administrators, the immediate inventory question is not merely whether the fleet contains iPhones. It is whether the organization’s mobile-device-management policies permit delayed OS updates, allow developer mode where it is unnecessary, or tolerate unreviewed enterprise-distributed apps. The iOS 26.6 bulletin makes the cost of those exceptions clearer.
Apple also patched an Accessibility issue affecting iPhone Mirroring that could expose sensitive information to someone with physical access. That does not have the same remote attack profile, but it is relevant in shared workspaces, repair depots, travel scenarios, and environments where an unlocked Mac may be paired with a nearby iPhone.
WebKit has a large patch set, but the claims need precision
WebKit, the engine beneath Safari and every iPhone browser, received a substantial share of iOS 26.6’s fixes. The patched issues include a visited-link privacy leak, interface spoofing, an iframe sandbox-policy violation, memory-safety bugs, and a flaw that could allow an app to read files outside its sandbox.CVE-2026-64713 addresses history sniffing: a website could determine whether a user had visited a particular link. CVE-2026-64728 could let malicious web content violate an iframe sandboxing policy, while CVE-2026-64730 addresses UI spoofing through framed malicious content. CVE-2026-43821 affects WebKit access controls and could allow an app to read files outside its sandbox.
The research credits in Apple’s bulletin have attracted understandable attention. Apple credits Milad Nasr and Nicholas Carlini “with Claude, Anthropic” for CVE-2026-64757, a WebKit memory-corruption issue that could crash Safari when it processes malicious web content. Apple’s entry does not say Claude independently discovered the bug, nor does it establish an automated exploitation capability. It records the researchers’ attribution in the advisory.
Similarly, Apple credits contributors “using GLM from Z.AI” on CVE-2026-64783, a WebKit use-after-free issue that could crash Safari. These credits show AI-assisted security work appearing in Apple’s public acknowledgments. They do not prove the broader claim that AI has caused vulnerability discovery to “skyrocket,” and Apple has published no metric in this release connecting AI tools to a July total of 210 CVEs.
The same caution applies to claims about Codex. Apple’s iOS 26.6 advisory includes Codex Security in its additional-recognition section for WebKit Canvas, but additional recognition is not a CVE assignment and does not identify a specific watchOS discovery. Apple’s security documentation credits assistance; it does not provide a detailed methodology for how each tool or researcher contributed.
A proof of concept exists for one bundled component, but exploitation is unconfirmed
There is one wrinkle in the broader July Apple patch cycle. Hong Kong’s government incident-response team issued a high-threat alert covering Apple’s coordinated updates and said reports indicated proof-of-concept exploit code was available for CVE-2026-3783, an information-disclosure vulnerability in curl.Apple’s iOS 26.6 advisory lists CVE-2026-3783 and CVE-2026-3784 under curl. The impact is that authentication credentials may be sent to a server on another origin. Apple describes it as an open-source vulnerability for which the CVE was assigned by a third party.
A proof of concept is not evidence of widespread exploitation, and neither Apple nor MacRumors has reported active attacks against iOS 26.6’s patched vulnerabilities. Still, it narrows the usual gap between publication and practical testing. The combined release covered iOS and iPadOS 26.6, macOS Tahoe 26.6, macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, watchOS 26.6, tvOS 26.6, visionOS 26.6, and Safari 26.6; leaving any of those behind creates inconsistent protection for users who move data among Apple devices.
The user-facing changes are small, and the upgrade case is security
iOS 26.6 does include a few visible or preparatory changes. Apple says it optimizes the Spotlight index ahead of iOS 27, expected in September 2026. MacRumors and 9to5Mac also reported a new “Blocked Contacts Limit Reached” alert, which tells users to remove an existing blocked contact before adding another once the device’s undisclosed cap has been reached.The update does not, however, substantiate reports of an enabled anti-snatching lock feature, a universally documented download size, or a guaranteed five-to-eight-minute installation window. Those vary by device, storage state, network conditions, and Apple’s staged delivery. Apple’s published release information emphasizes security fixes and Spotlight preparation, not a long list of new iPhone features.
Install iOS 26.6 through Settings > General > Software Update, then verify companion devices are patched to their respective July releases. For a Windows-managed environment, that means checking iPhones and iPads through MDM compliance reporting rather than assuming that an employee’s iPhone update also protected their Apple Watch, Mac, or Safari installation.
The key consequence is simple: iOS 26.6 does not appear to be a live zero-day emergency, but it patches flaws that can provide arbitrary code execution, kernel-level execution, root privilege, code-signing bypass, browser privacy leakage, and sandbox escape. On August 2, 2026, an iPhone still running a pre-26.6 build is missing all 87 CVE fixes Apple has now made public.
References
- Primary source: secnews.gr
Published: 2026-08-01T16:00:00+00:00
IOS 26.6: 87 Security Vulnerabilities Fixed [July 2026]
iOS 26.6 security update: 87 CVEs fixed. Critical RCEs in ImageIO, WebKit, kernel. Role of Claude AI and OpenAI Codex in discovery.www.secnews.gr - Related coverage: support.apple.com
About the security content of iOS 26.6 and iPadOS 26.6 - Apple Support
This document describes the security content of iOS 26.6 and iPadOS 26.6.support.apple.com - Related coverage: support.apple.com
About the security content of iOS 26.5.2 and iPadOS 26.5.2 - Apple Support
This update delivers security fixes that were first made available in the iOS 26.6 and iPadOS 26.6 betas. This document describes the security content of iOS 26.5.2 and iPadOS 26.5.2.support.apple.com - Related coverage: nvd.nist.gov
NVD - CVE-2026-16517
nvd.nist.gov
- Related coverage: macrumors.com
Update Now: iOS 26.6 and macOS Tahoe 26.6 Patch Hundreds of Security Flaws
Apple today released iOS 26.6, iPadOS 26.6, and macOS Tahoe 26.6, all of which have a long list of security fixes. iOS 26.6 and iPadOS 26.6 address almost 90 security vulnerabilities affecting everything from the App Store to the Neural Engine. Multiple kernel and WebKit vulnerabilities were...www.macrumors.com - Related coverage: 9to5mac.com
Apple fixes over 75 security issues with your iPhone and 150+ for Mac, update now - 9to5Mac
Following the release of iOS 26.6, iPadOS 26.6, and related software updates, Apple has detailed a huge number of security...9to5mac.com - Related coverage: nvd.nist.gov
NVD - CVE-2026-28973
nvd.nist.gov
- Related coverage: developer.apple.com
Releases - Apple Developer
Get the latest operating system releases and learn about updates to App Store Connect, TestFlight, and other developer tools.developer.apple.com
- Related coverage: developer.apple.com
Releases - Apple Developer
Get the latest operating system releases and learn about updates to App Store Connect, TestFlight, and other developer tools. - Related coverage: malwarebytes.com
Update your iPhone, iPad and Mac to fix Apple security holes | Malwarebytes
Apple issued a large July security update with several image processing related vulnerabilities that could compromise your device.www.malwarebytes.com - Related coverage: itpro.com
Apple is speeding up software patching due to AI security concerns – here’s what you need to know | IT Pro
Apple is speeding up its software patching processes amid rising concerns that AI is helping hackers to spot and exploit flaws at a far quicker pace.www.itpro.com