Skip to main content
CVE-2026-59632VulnerabilityPublished

In RespondReceivedMessage of MtsMessageController.cpp, there is a possible way to trigger memory exhaustion via an

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-59632· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 11 Nov 2026, 01:20 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GoogleAndroidAffected
  • =Android kernel
Fixed in–

Description

A vulnerability in the RespondReceivedMessage function of MtsMessageController.cpp allows remote attackers to cause memory exhaustion via an undrained message queue triggered by type confusion. This can result in a denial of service without requiring user interaction or additional privileges.

References

Community reviews

Loading reviews…