VulnerabilityPublished 2 Nov 2026

CVE-2026-20584: MediaTek chipset · Out-of-bounds Write

Affects MediaTek chipsetSource CVE Database V5

Compare

Not known to be exploited.

Data as of 2 Nov 2026, 02:58 UTC

Severity

High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 1 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
MediaTek, Inc.MediaTek chipset	Affected MT6739 – MT6993 29 affected builds	Fixed in–

AI-suggested

A patch identified as ALPS11411916 exists to address this vulnerability. Users and vendors should apply this official fix to affected MediaTek chipset versions. Since the vulnerability requires System privileges to exploit, limiting access to such privileges can reduce risk until patched.

Description

CVE-2026-20584 is a vulnerability in MediaTek chipsets caused by a missing bounds check in the USB component, leading to a possible out-of-bounds write and memory corruption. Exploitation does not require user interaction but requires the attacker to already have System privileges. This flaw could enable local escalation of privilege. A patch identified as ALPS11411916 addresses this issue.

Impact

Successful exploitation can lead to local escalation of privilege through memory corruption caused by an out-of-bounds write. The attacker must already have System privileges, so the vulnerability does not enable initial remote compromise or privilege gain from a lower privilege level. No user interaction is required for exploitation.

Summary

This vulnerability (CWE-787) involves an out-of-bounds write in the USB subsystem of MediaTek chipsets due to a missing bounds check. The flaw allows memory corruption that could be exploited by an attacker with existing System privileges to escalate their privileges locally. The affected products include multiple MediaTek chipset models such as MT6739, MT6761, MT6765, MT6768, MT6769, MT6781, MT6789, MT6833, MT6835, MT6853, MT6855, MT6858, MT6877, MT6878, MT6879, MT6881, MT6883, MT6885, MT6886, and MT6889. The vendor has assigned a patch ID (ALPS11411916) for remediation, though no direct patch links are provided in the data.

CWE-787Out-of-bounds Write (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #5
The product writes data past the end, or before the beginning, of the intended buffer.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

mediatek.com/product-security-bulletin/November-2026 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Nov 2026, 02:47 UTC

WeaknessesCWE-787

Technical details

References

Community reviews

Related threats