Cybersecurity

CISA Flags an Apple WebKit Bug Still Unpatched on Many Devices: A Mac, iPhone and iPad Update Checklist

CISA added Apple CVE-2024-27834 to its Known Exploited Vulnerabilities catalog on Nov. 4, 2026, with a Nov. 18 federal due date. It is an improper authentication / Pointer Authentication bypass when an attacker already has arbitrary read and write. Checklist for SMB offices with Macs, iPhones and iPads.

On November 4, 2026, CISA added CVE-2024-27834 — an Apple improper authentication vulnerability affecting multiple products — to its Known Exploited Vulnerabilities (KEV) catalog. Federal agencies have a due date of November 18, 2026. CISA lists ransomware use as Unknown and forensic triage required as No. If your office still has Macs, iPhones or iPads below the fixed releases from May 2024, this is a patch-priority item, not a tomorrow problem.

What CISA and NVD say

CISA's Nov. 4 alert names CVE-2024-27834 as "Apple Multiple Products Improper Authentication Vulnerability." The KEV entry describes it as an improper authentication issue in Apple iOS, iPadOS, macOS, Safari, tvOS and watchOS that could allow an attacker with arbitrary read and write capability to bypass Pointer Authentication. Related CWE is CWE-287. Known to be used in ransomware campaigns: Unknown. Forensic triage required per BOD 26-04: No. Date added: 2026-11-04. Due date: 2026-11-18.

NVD describes the same issue: "The issue was addressed with improved checks. This issue is fixed in Safari 17.5, iOS 16.7.8 and iPadOS 16.7.8, iOS 17.5 and iPadOS 17.5, macOS Sonoma 14.5, tvOS 17.5, watchOS 10.5. An attacker with arbitrary read and write capability may be able to bypass Pointer Authentication." NVD rates it CVSS 3.1 5.5 Medium (AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N). That score describes the standalone flaw; CISA added it because of evidence of active exploitation, not because the CVSS number is "critical."

What we are not claiming: Apple's advisories frame this as a Pointer Authentication (PAC) bypass for an attacker who already has arbitrary read and write — not as a remote one-click "anyone on the internet owns your Mac" bug by itself. Do not overclaim remote code execution from this CVE alone. Treat it as a KEV that still needs the fixed release installed.

What Apple fixed (May 2024)

Apple's security content notes for iOS/iPadOS 17.5, iOS/iPadOS 16.7.8, macOS Sonoma 14.5, Safari 17.5, and related tvOS/watchOS releases (all dated around May 13, 2024) list CVE-2024-27834 under WebKit with this impact wording: an attacker with arbitrary read and write capability may be able to bypass Pointer Authentication. The issue was addressed with improved checks. Credit: Manfred Paul working with Trend Micro's Zero Day Initiative.

If a device is already on a later supported release that includes those fixes (or newer), you are past the original May 2024 bar. The operational problem CISA is highlighting is offices that never applied those updates — common on shared iPads, older Macs kept on Sonoma without 14.5, or Safari left behind on Monterey/Ventura.

Why this matters for mixed SMB offices

Legal, financial, engineering, nonprofit, dental and medical teams often mix company Macs with BYOD iPhones and shared iPads for check-in or floor use. A medium CVSS score is easy to deprioritize next to ransomware headlines. KEV listing is the opposite signal: someone is exploiting it in the wild, and federal agencies are on a two-week clock. Your insurance questionnaire and cyber policy will care more about "did you patch known-exploited CVEs" than about the 5.5 number.

What to do this week

  1. Inventory Apple devices that touch firm data. Company Macs, iPhones, iPads, and any BYOD devices that open mail, VPN, practice or case systems, or browser sessions with client data. Note OS version and whether Safari is managed separately on older macOS.
  2. Confirm you are at or above the fixed releases. Minimum bars from Apple's advisories: iOS/iPadOS 17.5 (or 16.7.8 on older devices that stayed on 16.x), macOS Sonoma 14.5, Safari 17.5 on Monterey/Ventura, tvOS 17.5, watchOS 10.5. Prefer current supported updates when the device can take them.
  3. Push updates through your MDM or a written owner list. Shared iPads and "that one Mac in accounting" are where lag shows up. Require a screenshot or MDM compliance report, not a verbal "I think it's updated."
  4. Keep browser and OS updates on the same cadence. This CVE lives in WebKit. Safari updates on older macOS matter even when the Mac OS itself is slower to move.
  5. Do not invent a forensic fire drill from the KEV alone. CISA marks forensic triage required as No for this entry. Still, if a device was suspicious before patching (unexpected profiles, unknown MDM, odd browser extensions), handle that as a normal incident — separate from the patch itself.
  6. Brief staff in plain English. Update prompts are expected; unexpected links about "Apple emergency patch" that ask for passwords or remote access are not. Type settings paths yourself.
  7. Record the work. Note versions before/after and who owns each device. That list is what you show an auditor, insurer or client security questionnaire later.

The takeaway for IT decision-makers

KEV is a priority queue, not a severity brag. CVE-2024-27834 is a PAC bypass that assumes the attacker already has arbitrary read and write — serious in a chain, not a reason to panic-reimage every phone. Get every Mac, iPhone and iPad that holds firm data onto the fixed releases, prove it, and move on. If you want help building that inventory or pushing updates across a mixed office, Brotherly Technology can help.

Sources

One accountable technology partner.

Tell us what's slowing your team down. We'll show you exactly how we'd fix it — no pressure, no jargon.

Book a Free Consultation
Book a Free Consultation