Quick answers
- Is CVE-2026-20524 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-20524 being exploited in the wild.
- How severe is CVE-2026-20524?
- High severity, with a CVSS score of 8.4, published 5 October 2026.
- Which products and versions are affected?
- MediaTek Dimensity 5G <UNKNOWN>; MediaTek Helio 4G <UNKNOWN>.
- Is there a fix for CVE-2026-20524?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-20524 attacked?
- It is attacked with local access, in device firmware.
- Am I affected by CVE-2026-20524?
- Check whether you run MediaTek Dimensity 5G or MediaTek Helio 4G at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a memory corruption issue stemming from improper input validation in the APU component. It allows local privilege escalation with no additional execution privileges required and no user interaction needed. MediaTek assigned Patch ID ALPS11249004 and Issue ID MSV-9170; the exact attack preconditions and whether a patch is available in released products are not detailed in the available advisory materials.
Affected products
- MediaTek Dimensity 5G <UNKNOWN>
- MediaTek Helio 4G <UNKNOWN>
Timeline
- 2026-10-05: disclosed