Skip to content
Blog

Apple · iOS · iPadOS

Apple CVE-2024-27834 in CISA KEV: Pointer Authentication Bypass on iOS, macOS and Safari

CVE-2024-27834: Pointer Authentication bypass in Safari, iOS, iPadOS, macOS, tvOS and watchOS, fixed in May 2024, added to CISA KEV on November 4, 2026.

5 min readCVE-2024-27834

CVE-2024-27834 was published by NVD on May 14, 2024, the day Apple shipped Safari 17.5, iOS 17.5 and macOS Sonoma 14.5. It entered the CISA KEV catalog on November 4, 2026, two and a half years later, with a deadline of November 18, 2026.

The NVD score is modest: 5.5 (MEDIUM), local access. But what the flaw defeats is anything but minor: Pointer Authentication, one of the hardware protections that make exploiting Apple silicon so expensive.

It's the second Apple KEV addition in just over a month, after CoreGraphics CVE-2026-86950 in late September.


The Vulnerability

FieldValue
CVECVE-2024-27834
CVSS 3.1 (NVD and Apple)5.5 (MEDIUM) — AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
TypeImproper authentication (CWE-287)
PrerequisiteArbitrary read and write capability already obtained
NVD publication2024-05-14
Added to CISA KEV2026-11-04
CISA deadline2026-11-18
Known ransomware useUnknown

NVD description:

The issue was addressed with improved checks. […] An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication.

What Pointer Authentication Protects

On Apple's recent ARM chips, Pointer Authentication (PAC) cryptographically signs sensitive pointers: return addresses, function pointers. An attacker who corrupts memory can't just swap a pointer for an address of their choosing: the signature would no longer match and the process would crash.

In other words, memory corruption alone is no longer enough to hijack execution. You also need a way to get around PAC. That's exactly what CVE-2024-27834 provides.

One Link in an Exploit Chain

The description is explicit: the attacker must already have arbitrary read/write. So the flaw is not useful on its own. Our reading, and it is an inference: this is the second link of a chain, after a memory corruption bug (typically in the web rendering engine, which would explain why Safari and WebKitGTK are on the list) and before a possible privilege escalation.

That also explains the score: AV:L and PR:L describe the flaw in isolation, not the full chain it plugs into.

Among the NVD references is a Sekoia blog post about watering-hole attacks targeting mobile devices with n-day exploits, meaning already-patched flaws. The post's title attributes them to APT29. Neither NVD nor the KEV entry describes the campaign: for the details, that post is the place to look.


Affected and Fixed Versions

Apple lists the fixed versions in the NVD description:

ProductFixed version (Apple)
Safari17.5
iOS and iPadOS 1717.5
iOS and iPadOS 1616.7.8
macOS Sonoma14.5
tvOS17.5
watchOS10.5

The NVD configuration also covers non-Apple WebKit engines:

ProductFirst version outside the range (NVD)
WebKitGTK2.44.2
WPE WebKit2.44.2
Fedora39 and 40 (WebKit packages)

⚠️ The WebKitGTK and WPE numbers are bounds from NVD, not necessarily the version to install: follow your distribution's updates. On the Apple side, the security bulletins cited by NVD (support.apple.com, references 120896 through 120905) give per-platform details.

A release from May 2024 has long been superseded. In practice, the exposure is mostly:

  • stuck devices on an old version (un-updated iPhones or iPads, Macs left on Sonoma 14.4 or earlier);
  • Linux workstations with an outdated WebKitGTK (GTK apps embedding a web engine, mail clients, WebKit-based browsers);
  • embedded systems built on WPE WebKit.

Why a KEV Addition Two Years Later

CISA only adds a flaw to the catalog based on observed exploitation. A late entry doesn't mean exploitation is recent, it means it's now documented. For your fleet, the consequence is the same: any device still below the versions above is a known target.

The KEV entry also points to the forensic triage requirements of directive BOD 26-04: CISA asks you to check for compromise, not just to update.


Detection

  • OS version inventory for iOS, iPadOS, macOS, tvOS and watchOS from your MDM: anything below the fixed versions is in scope
  • Unmanaged devices reaching company resources (mail, VPN): that's usually where old versions linger
  • WebKitGTK versions on Linux workstations:
# Debian / Ubuntu
dpkg -l | grep -i webkit2gtk
# Fedora / RHEL
rpm -qa | grep -i webkit
# macOS
sw_vers

Mitigation

1. Update

Current version of each platform, or at least the versions in the table. The CISA deadline is November 18, 2026.

2. Deal with devices that can't be updated anymore

A device that no longer receives updates will never be fixed. Cut it off from company data, or replace it.

3. Enforce a minimum version

Set a minimum OS version in your MDM for access to resources (mail, business apps). That's what keeps a forgotten device from staying connected for two years.

4. High-risk profiles

For exposed users (executives, legal, teams dealing with state-level adversaries), Apple offers Lockdown Mode, which sharply reduces the browser's attack surface.


Why Continuously Monitor Your Apple Fleet

A MEDIUM flaw fixed in 2024 no longer shows up on any dashboard. Its KEV entry two years later changes nothing for up-to-date devices, and everything for the ones that aren't: provided you know which ones those are.

With cveo.tech, inventory your systems with their exact versions and get an alert as soon as a CVE affecting them enters the CISA KEV catalog, regardless of its age or score.

Know which CVEs hit the versions you run.

Add the product and its version: cveo.tech lists the CVEs that affect it right away, then alerts you by email when a new one affects it — including before NVD has finished its analysis. Free, an account is all it takes.

Every Monday

The week's critical CVEs, in your inbox

One email a week: the CVSS ≥ 9 vulnerabilities published in the last seven days, plus our latest analyses. Nothing else.

Double opt-in by email. Unsubscribe in one click, any time.