Cut-paper illustration of a row of Apple devices, a phone, a tablet and a laptop with green checkmarks, an older phone with a red warning badge, and a clipboard checklist beside them

On November 4, 2026, CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog, with a remediation due date of November 18. Apple shipped the fix for this flaw on May 13, 2024. That is two and a half years between the patch and the exploited listing, and that gap is the whole story.

This is not a new vulnerability. It is an old patch that a lot of devices never took, now being used in a live campaign. If you manage Apple devices, the useful question is not how the flaw works. It is which of your devices are still below the fixed build, and what you do about them this week.

What the flaw actually is

CVE-2024-27834 is a WebKit improper authentication flaw, CWE-287, scored 5.5 Medium by NVD. Apple's own wording is plain: "An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication." It was credited to Manfred Paul working with Trend Micro's Zero Day Initiative, and tracked as WebKit Bugzilla 272750.

Pointer Authentication is the hardware check on Apple silicon that makes it hard for an attacker to forge the pointers their exploit needs. Bypassing it does not get an attacker into a device by itself. It only matters once they already have code running. On its own it does nothing. Its value is as the second link in a chain, and someone has now built that chain and put it into production.

The chain that made it matter

On November 4, 2026, Sekoia published "Poisoned Source," a report on a large watering-hole campaign discovered in mid-October. The campaign reaches visitors through three delivery vectors: malicious JavaScript injected into compromised legitimate websites, lookalike AiTM domains that proxy the real site (america250.holiday in front of america250.org, and theowo.club in front of Raffles London at The OWO), and a supply-chain compromise of the Plerdy SEO Tracker between August 27 and September 3, 2026, which pushed the loader onto thousands of sites at once.

Every road leads to the same profiling script. It reads the visitor's OS and browser version, then serves a platform-matched exploit chain with no click and no download. The chain that uses this flaw is Class A: it targets iOS 16.7, and should work from iOS 16.0 to 17.4. It pairs CVE-2025-43529, which gets code running, with CVE-2024-27834, which gets past Pointer Authentication. The payload steals browser cookies. There is no persistence, and every flaw in all three chains is an n-day. A user running an up-to-date operating system is safe from these attacks.

Two honest caveats belong here. Sekoia assesses with moderate to high confidence that the campaign was conducted by APT29, also tracked as Midnight Blizzard and Cozy Bear. That is an assessment, not proven fact, and CISA names no attacker and does not tie its listing to Sekoia's report. It also remains unclear whether the attackers targeted specific visitors or cast the net wide. Sekoia named the delivery infrastructure it found, but it published no victim list and confirmed no compromise of any named organization.

The fixed builds

Apple fixed this flaw in the May 13, 2024 releases. The fixed floors, confirmed across Apple's advisories and the NVD record:

Product Fixed build
iPhone / iPad iOS / iPadOS 17.5
iPhone / iPad that cannot run iOS 17 iOS / iPadOS 16.7.8
Mac macOS Sonoma 14.5
Mac on Monterey or Ventura Safari 17.5
Apple TV tvOS 17.5
Apple Watch watchOS 10.5

Note the second row. iPhone 8 and iPhone X hardware is capped at iOS 16, and those devices are only safe on 16.7.8. A phone that stopped getting major updates did not stop needing security updates. That distinction is where most fleets quietly go wrong.

The fleet check

This is a tutorial, so here is the actual work. It takes an afternoon, and most of it is inventory, not patching.

  1. Pull the inventory from your MDM. In Addigy or whatever you use, export every Apple device with its OS version and build number. Sort by OS version, oldest first. Do not trust the count of devices that check in regularly. The ones that never check in are the ones that matter.
  2. Flag everything below the fixed floors. Anything on iOS below 17.5 (or below 16.7.8 on hardware capped at iOS 16), any Mac below Sonoma 14.5, any Monterey or Ventura Mac with Safari below 17.5. That is your list. Count it before you start fixing it, so you know when you are done.
  3. Go looking for the devices that are not in the list. The drawer phone kept as a spare. The shop-floor iPad that runs one app and never gets touched. The Ventura Mac in the corner office because its owner hates the Sonoma redesign. The test iPhone someone borrowed two years ago. These are the devices that make a fleet check worth doing, because the MDM report will not find them for you.
  4. Patch or retire, device by device. Push the update through MDM where you can. For the ones that cannot take the update, decide: upgrade the hardware, or take the device off the network and out of browsing duty. A phone that cannot be patched and still browses the web is an accepted risk, and it should be written down as one, not left as an accident.
  5. Re-authenticate where it matters. Patching closes the hole. It does not revoke a cookie that was already stolen. For any device that was below the fixed build and browses real sites, treat its sessions as exposed: sign out of the important accounts, sign back in, and rotate the sessions that matter. This is the step people skip.
  6. Set the deadline. November 18 binds only US federal agencies under BOD 26-04. You are probably not one. Use it anyway as your internal deadline, because the exploitation is already public and the delivery infrastructure is already built. Two weeks is a reasonable window for a fleet check of this size, and a hard date is what keeps it from becoming next quarter's work.

Do not burn the week hunting your logs for indicators. Sekoia named the delivery infrastructure, but the compromised sites are described by type rather than named, so there is no list to audit your fleet's browsing against. There is no clean detection shortcut here. The check is the inventory, and the fix is the patch.

The durable idea

A patch that shipped two and a half years ago can still be the urgent item on your list, because a patch only protects the devices that installed it. The industry talks about zero-days because they are dramatic. The unglamorous truth is that most real exposure is an n-day on a device nobody looked at in a while. The fleet check is boring, it takes an afternoon, and it is the whole job.

Sources