Quick answers
- Is CVE-2026-56952 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56952 being exploited in the wild.
- How severe is CVE-2026-56952?
- Medium severity, with a CVSS score of 6.7, published 6 October 2026.
- Which products and versions are affected?
- Google Pixel Devices All supported versions prior to 2026-10-05 security patch.
- Is there a fix for CVE-2026-56952?
- Yes: fixed in Android security patch level 2026-10-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-56952 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-56952?
- Check whether you run Google Pixel Devices at an affected version. 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
Technical details
The vulnerability exists in platform_msg_handler_init() in default_msg_handlers.c due to a missing authorization check. A local attacker with system-level execution privileges can bypass permission controls in the GDMC component to gain elevated access. No user interaction is required for exploitation.
Affected products
- Google Pixel devices All supported versions prior to 2026-10-05 security patch
Timeline
- 2026-10-06: disclosed
- 2026-10-05: patched