Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2016-1823: Memory Corruption in IOHIDDevice::handleReportWithTime (Apple iOS/OS X/tvOS/watchOS)

Published May 20, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3
EPSS4.9%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Apple
IdentifiersCVE-2016-1823CWE-704

CVE-2016-1823 is a memory corruption vulnerability in the IOHIDDevice::handleReportWithTime function present in Apple iOS before 9.3.2, OS X before 10.11.5, tvOS before 9.2.1, and watchOS before 2.2.1. The vulnerability is triggered by a crafted IOHIDReportType enum value, which leads to an incorrect cast and results in an out-of-bounds read and potential memory corruption. This can allow an attacker to execute arbitrary code in a privileged context or cause a denial of service.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an attacker to execute arbitrary code with elevated privileges or cause a denial of service via memory corruption. The vulnerability can be triggered remotely if the attacker can supply a crafted IOHIDReportType to the vulnerable function.

Mitigation

If you can’t patch tonight, do this now.

Restrict access to the IOHID subsystem to trusted code only, and monitor for abnormal HID report activity. Apply the vendor patch as soon as possible to fully mitigate the vulnerability.

Remediation

Patch, then assume compromise.

Upgrade to iOS 9.3.2, OS X 10.11.5, tvOS 9.2.1, or watchOS 2.2.1 or later, where the vulnerability has been patched by Apple.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AppleIphone Osoperating_system
AppleMac Os Xoperating_system
AppleTvosoperating_system
AppleWatchosoperating_system
FAQ

Frequently asked questions

Is CVE-2016-1823 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2016-1823 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-1823?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2016-1823.
Is there a patch for CVE-2016-1823?
Upgrade to iOS 9.3.2, OS X 10.11.5, tvOS 9.2.1, or watchOS 2.2.1 or later, where the vulnerability has been patched by Apple.
What products are affected by CVE-2016-1823?
Apple Tvos, Apple Watchos, Apple Iphone Os, and Apple Mac Os X.
How severe is CVE-2016-1823?
CVE-2016-1823 has a CVSS v3 score of 7.8 (High) and an EPSS score of 4.9% (92nd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.