Quick answers
- Is CVE-2026-56936 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56936 being exploited in the wild.
- How severe is CVE-2026-56936?
- Medium severity, with a CVSS score of 6.8, published 6 October 2026.
- Which products and versions are affected?
- Google Pixel.
- Is there a fix for CVE-2026-56936?
- Yes: fixed in Android security patch level 2026-10-05 or later. Until then: Update your Pixel device to security patch level 2026-10-05 or later to address this vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56936 attacked?
- It is attacked with physical access, in device firmware.
- Am I affected by CVE-2026-56936?
- Check whether you run Google Pixel. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Android security patch level 2026-10-05 or later
Update your Pixel device to security patch level 2026-10-05 or later to address this vulnerability.
Technical details
The vulnerability is an out-of-bounds write in the wacom_hid_set_device_mode function of wacom_sys.c caused by missing bounds checking. This allows privilege escalation (EoP) through the Wacom HID subsystem with physical attack vector. The fix is available in the Android security patch level 2026-10-05 or later.
Affected products
- Google Pixel
Timeline
- 2026-10-06: disclosed