CVE-2026-20450 — In Modem, there is a possible system crash due to incorrect error handling. This could…

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.

1. Identify exposed assets running the affected vendor/product/version combinations (Mediatek MediaTek chipset, Mediatek Mt2735 Firmware, Mediatek Mt2737 Firmware…).
2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
3. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

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.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-617

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.29%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

• Not enough vector or weakness data: use the affected application’s logs as a starting point.

Timeline

What happened to this CVE, newest first.

• 2026
• Affected products added · mediatek, inc./mediatek chipset
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• SSVC assessment updated
  Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
• Record published
  Oct 13, 2026
• CVSS changed · 6.5
  Oct 13, 2026 · NIST National Vulnerability Database
• Source status changed · → Analyzed
  Oct 13, 2026 · NIST National Vulnerability Database
• Record created in this database
  Oct 13, 2026 · NIST National Vulnerability Database
• CVE published
  May 4, 2026 · MediaTek

Source activity

Repeated readings are counted rather than listed.

• 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

1 on the record

• corp.mediatek.com/product-security-bulletin/May-2026
  Vendor Advisory, NIST National Vulnerability Database

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-20579 Out-of-bounds Write in Mediatek Mt2718 Firmware 10d
• Medium CVE-2026-20587 Type Confusion 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-20541 In Modem, there is a possible out of bounds read due to a missing permission 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-20450 is "In Modem, there is a possible system crash due to incorrect error handling. This could…", 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.29% 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.