CVE-2026-84511High· 7.8▾ TwilightAn out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27, watchOS 27. Processing a maliciously…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 42.9 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
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.
Exploit-prediction probability, daily snapshots since Sep 15.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via NVD
0.2%
Last analysed / modified upstream
— → 7.8
none → high
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27, watchOS 27. Processing a maliciously crafted asset catalog may lead to unexpected process termination.
ipados < 27.0iphone_os < 27.0macos >= 15.0, < 15.8macos >= 26.0, < 26.7tvos < 27.0visionos < 27.0watchos < 27.0Upgrade past the affected range:
ipados 27.0iphone_os 27.0macos 26.7tvos 27.0visionos 27.0watchos 27.0Field changes observed since this record was first indexed.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-65344High· 7.8An out-of-bounds write issue was addressed with improved bounds checking
CVE-2026-84526Medium· 4.3An out-of-bounds write issue was addressed with improved bounds checking
CVE-2026-64752High· 7.3A memory corruption issue was addressed by removing the vulnerable code
CVE-2026-65414Critical· 9.8An out-of-bounds write issue was addressed with improved bounds checking
CVE-2026-28966Medium· 4.3An out-of-bounds write issue was addressed with improved bounds checking
CVE-2026-65395Medium· 6.5An out-of-bounds write issue was addressed with improved bounds checking