CyberSecBulletin
CVE-2026-20586NVD status: Analyzed

MediaTek chipset: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2026-20586 is a high-severity out-of-bounds write vulnerability in MediaTek chipset from MediaTek, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected MediaTek chipset versions: MT6768; MT6769; MT6789, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of MediaTek chipset you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on mediatek.com for workarounds and exact fixed builds.
  3. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  4. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
MediaTekMediaTek chipsetMT6768; MT6769; MT6789; MT6833; MT6855; MT6877; MT8771; MT8781; and 3 more rangesNot stated
MediaTekMt8910 FirmwareNot specified in the recordNot stated
MediaTekMt2718 FirmwareNot specified in the recordNot stated
MediaTekMt6768 FirmwareNot specified in the recordNot stated
MediaTekMt6789 FirmwareNot specified in the recordNot stated
MediaTekMt6769 FirmwareNot specified in the recordNot stated
MediaTekMt6833 FirmwareNot specified in the recordNot stated
MediaTekMt6855 FirmwareNot specified in the recordNot stated
MediaTekMt6877 FirmwareNot specified in the recordNot stated
MediaTekMt8186 FirmwareNot specified in the recordNot stated
MediaTekMt8188 FirmwareNot specified in the recordNot stated
MediaTekMt8189 FirmwareNot specified in the recordNot stated
MediaTekMt8195 FirmwareNot specified in the recordNot stated
MediaTekMt8196 FirmwareNot specified in the recordNot stated
MediaTekMt8367 FirmwareNot specified in the recordNot stated
MediaTekMt8391 FirmwareNot specified in the recordNot stated
MediaTekMt8395 FirmwareNot specified in the recordNot stated
MediaTekMt8668 FirmwareNot specified in the recordNot stated
MediaTekMt8676 FirmwareNot specified in the recordNot stated
MediaTekMt8678 FirmwareNot specified in the recordNot stated
MediaTekMt8696 FirmwareNot specified in the recordNot stated
MediaTekMt8781 FirmwareNot specified in the recordNot stated
MediaTekMt8788e FirmwareNot specified in the recordNot stated
MediaTekMt8792 FirmwareNot specified in the recordNot stated
MediaTekMt8793 FirmwareNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by CISA (ADP).

Official description

In vdec, there is a possible out of bounds write due to a missing bounds check. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS11383899; Issue ID: MSV-9614.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Out-of-bounds Write

The product writes data past the end, or before the beginning, of the intended buffer.

How developers prevent this class of flaw

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
  • 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 checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in MediaTek chipset

All MediaTek chipset vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.