CVE-2026-20403 — Out-of-bounds Write in Mediatek MediaTek chipset
In Modem, there is a possible system crash due to a missing bounds check. This could lead to remote denial of service, if a UE has connected to a rogue base station controlled by the attacker, with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: MOLY01689254 (Note: For N15 and NR16) / MOLY01689259 (Note: For NR17 and NR17R); Issue ID: MSV-4843.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Mediatek MediaTek chipset, Mediatek Nr15, Mediatek Nr16…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Mediatek | MediaTek chipset |
version MT6993version MT6893version MT6895version MT6896version MT6897version MT6899version MT6980version MT6983 and 34 moreversion MT6985version MT6989version MT6990version MT6991version MT6891version MT8673version MT8675version MT8676version MT8771version MT8791version MT8791Tversion MT8795Tversion MT8797version MT8798version MT8893version MT6890version MT2735version MT2737version MT6813version MT6815version MT6833version MT6835version MT6853version MT6855version MT6873version MT6875version MT6877version MT6878version MT6879version MT6880version MT6883version MT6885version MT6886version MT6889 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
| Mediatek | Nr15 | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Mediatek | Nr16 | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Mediatek | Nr17 | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
| Mediatek | Nr17r | versions not specified by the source | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 6.5 | CVSS 3.1 | Medium | 2.8 | 3.6 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 6.5 | CVSS 3.1 | Medium | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.24%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · mediatek, inc./mediatek chipset
- SSVC assessment updated
- Record published
- CVSS changed · 6.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-20589 Out-of-bounds Write in Mediatek Mt2718 Firmware 10d
- Medium CVE-2026-20588 Out-of-bounds Write in Mediatek Mt2718 Firmware 10d
- Medium CVE-2026-20543 In Modem, there is a possible information disclosure due to a logic error. This could… 10d
- Medium CVE-2026-20544 Out-of-bounds Write in Mediatek Mt8910 Firmware 10d
- High CVE-2026-20586 Out-of-bounds Write in Mediatek Mt8910 Firmware 10d
- Medium CVE-2026-20540 In Modem, there is a possible out of bounds read due to a missing bounds check. This… 10d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-20403 is "Out-of-bounds Write in Mediatek MediaTek chipset", rated Medium. It affects MediaTek chipset (Mediatek); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 6.5 describes technical severity. EPSS 0.24% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.