Known exploited
Not asserted
Disputed
No
Stale source
No
Conflicts
0

Affected products and versions

1 source assertion
{"defaultStatus":"unaffected","product":"MediaTek chipset","vendor":"MediaTek, Inc.","versions":[{"status":"affected","version":"MT6890"},{"status":"affected","version":"MT7915"},{"status":"affected","version":"MT7916"},{"status":"affected","version":"MT7981"},{"status":"affected","version":"MT7986"}]}
  • cve_program_cvelist_v5affected
    urn:baitaphish:normalized-source-record:v2:d880625fba4ea9f594633e45d1d1f2a9d7f50437e604d82a3340702820ac1653 · sha256:db8445e9213b6f7e… · /containers/cna/affected/0

Provider-owned CVSS observations

1 source assertion
{"metric":{"attackComplexity":"LOW","attackVector":"ADJACENT_NETWORK","availabilityImpact":"HIGH","baseScore":8.8,"baseSeverity":"HIGH","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"NONE","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"metric_type":"cvssV3_1"}
  • cve_program_cvelist_v5cvss
    urn:baitaphish:normalized-source-record:v2:d880625fba4ea9f594633e45d1d1f2a9d7f50437e604d82a3340702820ac1653 · sha256:db8445e9213b6f7e… · /containers/adp/0/metrics/0/cvssV3_1

CWE assertions

1 source assertion
{"cweId":"CWE-787","description":"CWE-787 Out-of-bounds Write","lang":"en","type":"CWE"}
  • cve_program_cvelist_v5cwe
    urn:baitaphish:normalized-source-record:v2:d880625fba4ea9f594633e45d1d1f2a9d7f50437e604d82a3340702820ac1653 · sha256:db8445e9213b6f7e… · /containers/cna/problemTypes/0/descriptions/0

Source references

1 source assertion
{"url":"https://corp.mediatek.com/product-security-bulletin/March-2026"}
  • cve_program_cvelist_v5reference
    urn:baitaphish:normalized-source-record:v2:d880625fba4ea9f594633e45d1d1f2a9d7f50437e604d82a3340702820ac1653 · sha256:db8445e9213b6f7e… · /containers/cna/references/0

Attribution and limitations

  • CVE Program CVEList V5: Reproduce the MITRE copyright designation and CVE license in copies. Source →

Provider severity values are preserved separately. Baitaphish does not convert them into a risk rating, infer affected products, or treat EPSS as observed exploitation.