Skip to content
nulltapE-reader edition

← All e-reader articles

3 min read

CISA Adds Exploited Apple WebKit Bypass to Its Priority List

The flaw needs prior read and write access before pointer authentication can be bypassed. Apple shipped fixes in 2024; compare installed Safari and OS releases across the fleet.

Read on the standard site

Illustration of a phone with a blue browser compass inside a dark metal ring, broken by a broad gap and red fragments.

CISA added Apple’s CVE-2024-27834 to its Known Exploited Vulnerabilities catalog on November 4, 2026. The WebKit flaw can let an attacker who already has arbitrary read and write capability bypass pointer authentication. Across iPhones, iPads, Macs, Apple TVs and Watches, an attacker with that access can weaken a defense that protects code pointers.

The catalog gives federal agencies a November 18 action date. Apple released fixes in May 2024, so the immediate job is to find devices that missed those releases, particularly older phones and Macs whose browser updates follow a different branch. CISA’s listing establishes exploitation. Apple’s release advisories give fleet owners specific patch thresholds to check.

The WebKit check attackers bypass

Pointer authentication helps protect code pointers from being altered and reused during an attack. Apple’s Safari security advisory states the impact precisely: “An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.” Apple says it addressed the WebKit issue with improved checks and credits Manfred Paul, working with Trend Micro’s Zero Day Initiative. The WebKit bug reference is 272750.

An attacker first needs the read and write capability Apple describes; the bypass then reduces the protection pointer authentication offers. A patch for this bypass addresses that later step. If independent evidence points to earlier device compromise, investigate that access separately. The Apple-authored CVE record lists the same precondition and fixed releases. CISA’s enrichment marks exploitation active and scores the flaw as a local attack requiring low privileges.

Apple shipped fixes across release branches

Apple’s original May 13, 2024 releases put the fix in Safari 17.5 for macOS Monterey and Ventura, iOS and iPadOS 16.7.8 for supported older devices, and iOS and iPadOS 17.5 for the newer branch. Its macOS Sonoma 14.5 advisory covers Sonoma, while the tvOS 17.5 and watchOS 10.5 advisories cover Apple TV and Apple Watch. These releases first fixed this flaw; keep each device on a supported, current release after the initial check.

For a mixed Mac fleet, record the installed Safari release on Monterey and Ventura as well as the installed macOS release on Sonoma. For iPhones and iPads, compare the installed branch against the corresponding Apple advisory and the device models it names; a 16.x device needs the 16.7.8 threshold, while a 17.x device needs 17.5. Apple TV and Watch inventories need their own tvOS and watchOS versions. Where a device cannot take a listed fixed release, plan a supported upgrade or remove it from the work it protects.

Compare fleet versions to Apple fixes

Pull the installed OS and, where applicable, Safari versions from device management. Segment the inventory by platform and branch; compare each group to Apple’s fixed releases above, then deploy a supported fixed or newer release to devices below the relevant threshold. Include unmanaged or intermittently connected devices in the follow-up list. After rollout, check the installed version, including on devices that were offline when updates were assigned.

CISA also asks stakeholders to evaluate each asset’s internet exposure and follow its risk-based patch guidance. Prioritize exposed devices for patching while checking separately for evidence of the arbitrary read and write capability Apple describes. Device-specific indicators for this bypass are unavailable here. For a suspicious device, use your incident process and device telemetry to investigate access that preceded the patch; version checks show whether the WebKit fix is installed.

Primary sources