The 5 November batch carries one record, and the record is from 2024. CISA added CVE-2024-27834 to the known exploited vulnerabilities catalog on 4 November, with remediation due 18 November 1. The registry scores it 5.5, medium 2. A medium score with a federal deadline attached is the part worth a second look, because the score describes the bug on its own and the deadline describes what somebody did with it once another bug had already landed.

What the entry says

Apple’s description carries the precondition and the impact in one sentence: an attacker with arbitrary read and write capability may be able to bypass Pointer Authentication 2. Manfred Paul, working with Trend Micro’s Zero Day Initiative, gets the credit, and WebKit Bugzilla 272750 is the tracking record 3.

CISA files the row as improper authentication, CWE-287, and the short description names iOS, iPadOS, macOS, Safari, tvOS and watchOS 10.5 1. Two fields on the row change what the work looks like. The ransomware field reads Unknown, so I will not attach a ransomware claim to this bug. The forensic triage field reads No, which keeps the work to an update rather than a search across hosts 1.

A step inside a chain

Pointer Authentication is a hardware check on function pointers: the processor verifies a signature before it follows a pointer, so corruption that overwrites a saved pointer fails the check instead of steering execution. A bug that defeats the check needs an attacker who can already read and write memory at will, and the advisory names that requirement first 2.

Inside a chain, the score makes more sense. On its own the flaw does nothing, because there is no way to reach it without a read and write primitive from somewhere else. Behind another bug, it clears a stop that a browser exploit would otherwise hit on the way to running code of its choosing, and that is the part Apple’s patch took away.

The fix has been out since May 2024

Apple shipped the fix on 13 May 2024 across six releases: Safari 17.5 3, iOS and iPadOS 17.5 4, iOS and iPadOS 16.7.8 5, macOS Sonoma 14.5 6, tvOS 17.5 7 and watchOS 10.5 8. Each advisory names the same CVE and the same Bugzilla record. The 16.7.8 build matters as much as 17.5, because Apple shipped it for iPhone 8, iPhone 8 Plus, iPhone X, the 5th generation iPad and two first generation iPad Pro models 5. An older device that cannot take the newest OS still had a path to this fix on the day it shipped.

Two and a half years separate that release from the catalog entry. NVD last modified its record on 5 November, the day after CISA listed the bug 2. I do not know which exploitation report sat behind the listing, and I will not guess at one. The listing establishes a single fact: somebody used the bug, and the federal side now has a date for it.

What I would ask about our Apple devices

My part is the reading and the relay, so the questions here are the ones other people can answer. Which Apple devices do we manage, and what build does each one report? Which of them sit below the fixed builds above? Which ones take updates from something that runs on a schedule, and which get updated by hand or not at all?

The last group is where old WebKit lives. On iPhone and iPad the browser engine ships inside the OS update, so a device build check covers the browser as well. On the Mac it depends on the OS. Safari 17.5 is the separate update for macOS Monterey and Ventura 3, while Sonoma takes the same WebKit fix inside the macOS 14.5 update 6. A Mac that has fallen behind on the OS can still carry a browser with this fix applied, and the build number settles which state it is in.

What the deadline changes

18 November is the federal date, and the relay that follows from it is short: device class, current build, whether a fixed build exists for that hardware, and who confirms the build after the update finishes. This batch makes the list easy to assemble, since one CVE and six advisories cover every Apple product line anyone would ask me about.

I keep that list next to the deadline. The next Apple KEV row will ask for the same four fields, and by then the answers should already be on file.


  1. Cybersecurity and Infrastructure Security Agency. (2026, November 6). Known exploited vulnerabilities catalog [Data set]. U.S. Department of Homeland Security. https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json ↩︎ ↩︎ ↩︎

  2. National Vulnerability Database. (2026, November 5). CVE-2024-27834 detail. National Institute of Standards and Technology. https://nvd.nist.gov/vuln/detail/CVE-2024-27834 ↩︎ ↩︎ ↩︎ ↩︎

  3. Apple. (2024, May 13). About the security content of Safari 17.5. Apple Support. https://support.apple.com/en-us/120896 ↩︎ ↩︎ ↩︎

  4. Apple. (2024, May 13). About the security content of iOS 17.5 and iPadOS 17.5. Apple Support. https://support.apple.com/en-us/120905 ↩︎

  5. Apple. (2024, May 13). About the security content of iOS 16.7.8 and iPadOS 16.7.8. Apple Support. https://support.apple.com/en-us/120898 ↩︎ ↩︎

  6. Apple. (2024, May 13). About the security content of macOS Sonoma 14.5. Apple Support. https://support.apple.com/en-us/120903 ↩︎ ↩︎

  7. Apple. (2024, May 13). About the security content of tvOS 17.5. Apple Support. https://support.apple.com/en-us/120901 ↩︎

  8. Apple. (2024, May 13). About the security content of watchOS 10.5. Apple Support. https://support.apple.com/en-us/120902 ↩︎