CVERadar
MEDIUM · CVSS 3.1 5.5Public PoCEPSS 0.15% (p3)Threat level 32

CVE-2026-84616: CVE-2026-84616: A type confusion issue was addressed with improved memory handling. This issue is fixed in…

apple · ipados · NVD published 2026-09-15 · posted 2026-09-16 · last modified 2026-09-18

What it is

A type confusion issue was addressed with improved memory handling. This issue is fixed in iOS 26.7 and iPadOS 26.7, iOS 27 and iPadOS 27, macOS Golden Gate 27, macOS Sequoia 15.8, macOS Tahoe 26.7, tvOS 27, visionOS 27, watchOS 27. An app may be able to cause unexpected system termination.

WeaknessCWE-441
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H (source: 134c704f-9b21-4f2e-91b3-4a467353bcc0)
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2026-09-16 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

1 public repositories from 1 accounts, first seen 2026-09-16. Most starred: Ping-2o/ios.CVE-2026-84616-84607 (10 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

  • apple ipados: upgrade to 26.7 or later
  • apple iphone os: upgrade to 26.7 or later
  • apple macos: upgrade to 15.8 or later (affected from 15.0)
  • apple macos: upgrade to 26.7 or later (affected from 26.0)
  • apple tvos: upgrade to 27.0 or later
  • apple visionos: upgrade to 27.0 or later
  • apple watchos: upgrade to 27.0 or later

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources