VulnerabilityPublished 2 Mar 2026Updated 30 Mar 2026

CVE-2026-20424: MediaTek chipset · Out-of-bounds Read

Affects MediaTek chipsetSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.4 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.4Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Mar 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 30 Oct 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 MT6991 – MT8793 5 affected builds	Fixed in–

AI-suggested

To mitigate CVE-2026-20424, organizations and device manufacturers should promptly apply the official patch provided by MediaTek (Patch ID: ALPS10320471) as soon as it becomes available. Since exploitation requires System-level privileges, enforcing strict access controls and privilege management on devices can reduce the risk of attackers reaching the required privilege level. Employing runtime protections such as memory safety checks, sandboxing, and integrity monitoring can help detect or prevent exploitation attempts. Regularly auditing and monitoring for unusual local activity may identify attempts to leverage this vulnerability. For device manufacturers, incorporating secure coding practices and thorough bounds checking in firmware and driver development is essential to prevent similar issues. End users should keep device firmware and operating systems updated to benefit from vendor patches. Additionally, organizations should consider threat modeling to understand how this vulnerability might be chained with others to escalate attacks.

Description

In display, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS10320471; Issue ID: MSV-5540.

Impact

The primary impact of CVE-2026-20424 is local information disclosure, which can aid attackers in further compromising affected devices by revealing sensitive memory contents such as cryptographic keys, credentials, or proprietary data. Since exploitation requires System privileges, the vulnerability mainly threatens environments where attackers have already gained elevated access, potentially enabling lateral movement or persistence. Devices using affected MediaTek chipsets—commonly found in smartphones, tablets, IoT devices, and embedded systems—may be at risk of data leakage. This can undermine confidentiality and trust in affected products, potentially leading to privacy violations, intellectual property theft, or aiding in further attacks. The lack of impact on integrity and availability limits the scope to confidentiality breaches. Organizations relying on these chipsets in critical infrastructure or consumer electronics should consider the risk of sensitive data exposure and the implications for compliance and user privacy.

CWE-125Out-of-bounds Read (opens in a new tab)
Base weaknessCWE Top 25 (2025): #8
The product reads data past the end, or before the beginning, of the intended buffer.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design · Language Selection
Use a language that provides appropriate memory abstractions.
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)
Attack patterns
Overread Buffers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Mar 2026, 19:38 UTC

WeaknessesCWE-125

Technical details

References

Community reviews

Related threats