On Nov. 4, 2026, CISA added CVE-2024-27834 to its Known Exploited Vulnerabilities catalog. That federal listing is the clean signal. Separately, security researchers published a report the same calendar day describing a watering-hole campaign that used the patched Apple flaw as one step in mobile info-stealing chains. Operators should keep those layers separate. CISA’s listing means there is evidence of active exploitation meeting KEV criteria. It does not, by itself, verify every payload detail in a vendor report, and it does not invent a fresh zero-day. Apple shipped fixes in May 2024. The practical work for fleets is deciding which Apple products and branches still need the applicable security update.
CISA Flags Exploitation of a Patched Apple Flaw
CISA’s Nov. 4 alert says it added one vulnerability to the KEV catalog “based on evidence of active exploitation”: CVE-2024-27834, described as an Apple multiple-products improper authentication issue. The catalog entry summarizes it as a flaw that could allow an attacker with arbitrary read and write capability to bypass pointer authentication. For Federal Civilian Executive Branch agencies, the KEV due date is Nov. 18, 2026. CISA also points agencies to Binding Operational Directive 26-04 on risk-based update prioritization. That directive binds FCEB agencies. CISA encourages other organizations to treat KEV items as high priority; that encouragement is not a private-sector statute.
Apple’s own notes place a fix for this CVE in May 2024. The iOS 16.7.8 and iPadOS 16.7.8 security content page, released May 13, 2024, lists CVE-2024-27834 under WebKit with the impact line that an attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. Apple credits Manfred Paul working with Trend Micro’s Zero Day Initiative. CISA’s listing concerns exploitation of an Apple flaw patched in 2024, not a brand-new unpatched bug. Other Apple product lines may list the same CVE on their own security-content pages; check the note that matches each device’s OS branch rather than assuming every numerically older build shares the same exposure.
One technical nuance matters for triage. Apple’s description frames CVE-2024-27834 as a bypass that assumes the attacker already has arbitrary read and write in the process. It is a second-stage primitive, not a lone drive-by by itself. That is why chain reporting matters when deciding how hard to push a short KEV due date.
What the Info-Stealing Research Shows
The info-stealing narrative comes from research, not from CISA’s one-line KEV announcement. In a Nov. 4, 2026 post titled Poisoned Source, Sekoia’s Threat Detection and Research team says it uncovered a large-scale watering-hole campaign in mid-October 2026. The report describes three delivery paths: JavaScript injection on compromised legitimate sites, lookalike domains, and a one-week compromise of the Ukrainian Plerdy analytics tracker between Aug. 27 and Sept. 3, 2026. A profiling script then received platform-specific n-day exploit chains without further user interaction, per Sekoia.
For the Apple PAC issue specifically, Sekoia maps a “Class A” chain aimed at iOS 16.7 that combines CVE-2025-43529 for WebKit remote code execution with CVE-2024-27834 as the Pointer Authentication bypass, then steals cookies. Sekoia also describes heavier iOS 18.5 and Android Chrome chains that collect broader device or Chrome data. Attribution in that report is hedged: “moderate to high confidence” that APT29, or a subgroup, conducted the campaign. That is a researcher assessment. CISA’s KEV alert does not name APT29, does not name Plerdy, and does not describe cookie theft.
Separate older context from this evidence. Apple documented the CVE-2024-27834 fix in its May 2024 release. Sekoia’s mid-October 2026 discovery and Nov. 4 writeup are the current campaign report that secondary coverage has tied to the KEV addition. Do not flatten 2024 patch history, 2026 watering-hole research, and CISA’s catalog decision into one sentence that claims CISA verified the stealer payload.
Closing the Gap Between Vendor Fix and Fleet Update
The following is my analysis as an operator, not a compliance order for private shops.
- Inventory Apple endpoints against the security note for each model and OS branch. Use Apple’s applicable security-content page for that product line to see whether CVE-2024-27834 appears and which release addressed it. Prefer current supported updates for that branch over chasing a single ancient minimum across every Apple device you own.
- Treat browsing as the exposure path. Sekoia’s model is watering-hole delivery into the browser stack. If a device can open Safari or Chrome on untrusted or third-party-scripted pages, matching the right WebKit or OS update matters more than whether the box is “internet facing” in the server sense.
- Prioritize KEV due dates for government fleets, and use them as a benchmark elsewhere. Nov. 18, 2026 is the FCEB due date on the catalog entry. Hypothetical: if you run a mixed civilian contractor shop that mirrors federal phones, aligning those phones to the applicable Apple fix by that date is a defensible change window, not because BOD 26-04 names you, but because the exploit evidence is already public.
- Hunt the researcher’s delivery patterns without over-claiming compromise. Look for odd analytics script changes, unexpected third-party JavaScript hosts, and devices whose OS branch still lacks the WebKit fix Apple documents for this CVE. Sekoia reports no persistence, but that does not undo cookie theft. My incident-response recommendation is to review affected sessions and revoke exposed session tokens, rather than treating a reboot as recovery.
- Keep the ticket language honest. Write “CISA KEV: CVE-2024-27834, evidence of active exploitation” on one line, and “Sekoia Poisoned Source: reported cookie-stealing chain using CVE-2024-27834” on another. Mixing them into “CISA says APT29 stole cookies” invents a quote CISA did not publish.
The vendor fix is old. The KEV listing is new. The stealer-chain detail belongs to the researchers who published it. Close the update gap on the Apple builds you still own, and keep the attribution labels as clean as the patch notes.









