CVE-2026-59603: Android MtsMessageController double free in message retry handling

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

A vulnerability in Android's messaging system can cause the process to crash due to a double free memory error during message retry handling. An attacker with network access can exploit this to remotely deny service to the device without needing special privileges. The crash prevents normal messaging functionality until the device is restarted.

Technologies: Google Android. Vendors: Google.

Quick answers

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

Technical details

A use-after-free vulnerability in MtsMessageController.cpp's RespondReceivedMessage function allows triggering a double free during message retry handling, causing process abort. The vulnerability is triggered over the network with no authentication or user interaction required, resulting in denial of service to the messaging subsystem.

Affected products

  • Google Android prior to 2026-11-05 security patch level

Timeline

  • 2026-11-10: disclosed
  • 2026-11-05: patched

References

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