# CVE-2026-56952: Android permission bypass in GDMC message handler

Source: https://junglewise.ai/threats/cve-2026-56952-in-platform-msg-handler-init-of-default-msg-handlers-c-there-is-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-06. Updated: 2026-10-06  
License: CC BY 4.0 with a link back

CVE-2026-56952 · Severity: medium · CVSS 6.7 · Published 2026-10-06

A permission check is missing in Android's GDMC (Google Device Message Component) message handler initialization, allowing a local attacker to escalate privileges to system level. This could enable unauthorized access to sensitive device functions and data without any user interaction.

Technologies: [Google Pixel Devices](https://junglewise.ai/threats/technologies/pixel-devices). Vendors: [Google](https://junglewise.ai/threats/vendors/google).

## 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

## References

- [https://source.android.com/docs/security/bulletin/pixel/2026/2026-10-01](https://source.android.com/docs/security/bulletin/pixel/2026/2026-10-01)

## Related threats

- [PowerVR GPU kernel use-after-free in fence identifier handling](https://junglewise.ai/threats/cve-2026-59609-in-fence-manager-extract-iif-of-fence-manager-c-there-is-a)
- [Google Pixel Face Auth TA privilege escalation in TzPipelineInputExtractor](https://junglewise.ai/threats/cve-2026-59607-in-tzpipelineinputextractor-of-tzpipelineinputextractor-cpp-there)
- [Pixel HWCodec Firmware heap buffer overflow in encoder](https://junglewise.ai/threats/cve-2026-59594-in-spm-alloc-of-encoder-there-is-a-possible-heap-buffer-overflow)
- [Pixel devices out-of-bounds write in graphics execution](https://junglewise.ai/threats/cve-2026-58804-in-executegraphcommand-of-multiple-files-there-is-a-possible-way)
- [ARM SMMU v3 stale stream table entry information disclosure](https://junglewise.ai/threats/cve-2026-58801-in-smmu-domain-config-s1-of-arm-smmu-v3-c-there-is-a-possible-way)
