CVE-2024-27834Medium· 5.5▾ Midnight⚠ Exploited in the wildPoC availableThe 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 ma…
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 30.3 · likelihood 0.1 · exploitation 25
A public proof-of-concept already exists for this vulnerability — see Exploit availability below.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the CISA ADP record, not NVD.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
Federal remediation due Nov 18, 2026
Last analysed / modified upstream
0.6%
Added to the CISA catalog on Nov 4, 2026. Federal remediation due Nov 18, 2026. View catalog ↗
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.
Safari < 17.5ios_and_ipados < 16.7.8ios_and_ipados < 17.5macOS < 14.5tvOS < 17.5watchOS < 10.5Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2024-27820High· 7.5The issue was addressed with improved memory handling
CVE-2025-43529High· 8.8A use-after-free issue was addressed with improved memory management
CVE-2023-43000High· 8.8A use-after-free issue was addressed with improved memory management
CVE-2025-31277High· 8.8The issue was addressed with improved memory handling
CVE-2026-112621High· 7.5An out-of-bounds write issue was addressed with improved bounds checking
CVE-2026-20643Medium· 5.4A cross-origin issue in the Navigation API was addressed with improved input validation