iOS, tvOS: limit execution permissions

Published · Updated · Digital strategy · 5 min read · By Cyber Intelligence Embassy

At a glance

iOS, tvOS: code execution. This 2026-07-28 case examines 9 version entries and 210 CVEs, documented releases and checks suited to mobile devices, using CERTFR-2026-AVI-0938.

AI illustration: a dark cybersecurity technology space with restrained golden lighting Illustration · fictional scene
In this article

Retrospective for 2026-07-28, compiled on 27 October 2026. The date identifies the day being analysed; source publication and revision dates are recorded below.

What this advisory changes in your environment

The starting point is CERTFR-2026-AVI-0938, published on 2026-07-28. Its scope includes iOS, tvOS, macOS Tahoe, macOS Sequoia, Safari, iPadOS, macOS Sonoma, visionOS, watchOS. Reported consequences are denial of service, data integrity compromise, code execution, security control bypass, loss of confidentiality, privilege escalation. These statements apply to the advisory’s scope; they do not assign every consequence to every product or CVE.

This case contains 9 version entries; CVE identifier count: 210. Track remediation by component: a successful overall update does not demonstrate that iOS and watchOS each received their respective fix.

Products and versions to examine

Reference
CERTFR-2026-AVI-0938
Source first published
2026-07-28
Latest source revision available for this day
2026-07-28
Named components
iOS, tvOS, macOS Tahoe, macOS Sequoia, Safari, iPadOS, macOS Sonoma, visionOS, watchOS
CVE identifiers
CVE-2026-43730, CVE-2026-64734, CVE-2026-28982, CVE-2026-43766, CVE-2026-43804, CVE-2026-43738, CVE-2026-43694, CVE-2026-43811, CVE-2026-43799, CVE-2026-43755, CVE-2026-64770, CVE-2026-43758, CVE-2026-43817, CVE-2026-64749, CVE-2026-64739, CVE-2026-43772, CVE-2026-43756, CVE-2026-64774, CVE-2026-64747, CVE-2026-43681, CVE-2026-43797, CVE-2026-64699, CVE-2026-43718, CVE-2026-64765 … (+186)
ComponentPublished condition
iOS< 26.6
tvOS< 26.6
macOS Tahoe< 26.6
macOS Sequoia< 15.7.8
Safari< 26.6
iPadOS< 26.6
macOS Sonoma< 14.8.8
visionOS< 26.6
watchOS< 26.6

For iOS, the published condition is “< 26.6”. Compare the version actually loaded with that condition within its own release branch. A fix installed on another edition of iOS, tvOS does not close this case.

Mechanism and prerequisites

Execution context matters as much as the flaw’s name. Distinguish operations available to a local user from those exposed remotely, then examine the permissions and secrets of the affected process.

The primary record CVE-2026-43730, published by apple, covers iOS and iPadOS, macOS, tvOS, visionOS, watchOS. The retained revision is dated 2026-07-28. Its scope is presented separately from the integrations and product groupings in CERTFR-2026-AVI-0938.

Choose the appropriate intervention

  1. Locate iOS instances, running releases and service owners. Record condition < 26.6 in the ticket alongside reference CERTFR-2026-AVI-0938.
  2. Compare the installed branch with the vendor’s iOS release notes. Prepare the package for that branch and a dependent-service test, retaining the pre-change state.
  3. After changing iOS, capture the loaded version again and verify the workflow below. Any exception needs an owner, an exposure-reduction measure and an expiry date.

Verify the fix in a real workflow

Validation scenario to adapt for iOS, tvOS: On a test device using iOS, record the system version and patch level after restart. Check managed applications, corporate network access and account recovery; distinguish application updates from operating-system updates. This is a proposed defensive check, not a claim that testing was performed against third-party systems.

Limit of case CERTFR-2026-AVI-0938: this analysis replaces neither vendor prerequisites nor investigation of your logs. Only documented versions are reproduced; no attack date or victim is invented.

Questions specific to this case

Which condition should be checked for iOS?

Advisory CERTFR-2026-AVI-0938 states: iOS — < 26.6. Check the edition and running release; do not extend the published boundary to branches absent from the advisory.

Why not use one fix for iOS and watchOS?

CERTFR-2026-AVI-0938 distinguishes these components within a scope containing 9 entries. Match each branch to its own update documentation and functional check.

What is still needed to assess iOS, tvOS exposure?

For iOS, tvOS, establish the running version, the path to the component and process permissions. The sources retained for CERTFR-2026-AVI-0938 do not establish every prerequisite or active exploitation.

Sources and related reading

Practical guide : Deploy phishing-resistant authentication with safe recovery

Explore the decision addressed in this case

Complete source advisory inventory

The article table may be an extract. These lists contain every affected-system entry and CVE in the specified advisory revision. They are not an inventory of your assets and do not map every CVE to every product.

Official source · CERTFR-2026-AVI-0938
Advisory revision : · Checked on :

Affected systems · 9

Original French wording is retained to avoid ambiguous translations of version conditions.

  1. iOS versions antérieures à 26.6
  2. tvOS versions antérieures à 26.6
  3. macOS Tahoe versions antérieures à 26.6
  4. macOS Sequoia versions antérieures à 15.7.8
  5. Safari versions antérieures à 26.6
  6. iPadOS versions antérieures à 26.6
  7. macOS Sonoma versions antérieures à 14.8.8
  8. visionOS versions antérieures à 26.6
  9. watchOS versions antérieures à 26.6
CVE identifiers · 210