CVE-2026-59632: Android framework memory exhaustion in message queue handling

CVE-2026-59632 · Severity: info · Published 2026-11-10

A vulnerability in Android's messaging framework allows remote attackers to exhaust device memory by sending specially crafted messages that are not properly drained from a queue, causing a denial of service. This could render affected devices unresponsive or force them to restart without requiring any special permissions or user interaction.

Technologies: Google Android. Vendors: Google.

Quick answers

Is CVE-2026-59632 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-59632 being exploited in the wild.
How severe is CVE-2026-59632?
Informational severity, published 10 November 2026.
Which products and versions are affected?
Google Android.
Is there a fix for CVE-2026-59632?
Yes: fixed in Android security patch level 2026-11-05 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-59632 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-2026-59632?
Check whether you run Google Android. 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-11-05 or later

Technical details

The vulnerability exists in MtsMessageController.cpp's RespondReceivedMessage function due to type confusion that prevents proper message queue drainage. An attacker can send network-accessible messages that accumulate in memory, leading to denial of service. No additional execution privileges are required and user interaction is not necessary for exploitation.

Affected products

  • Google Android

Timeline

  • 2026-11-10: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.