In gnss, there is a possible out of bounds write due to a missing bounds check.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects the listed MediaTek chipsets (MT2735, MT2737, MT6880, MT6890, MT6980D, MT6982, MT6986, MT6988, MT6990) in the gnss subcomponent.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
The vulnerability affects the GNSS (satellite navigation) component of a device's software, which is a MediaTek-based Android component in this description. An attacker with local access could trigger an out-of-bounds write that crashes the affected component, causing a local denial of service, and exploitation requires user interaction.
Read the original description
In gnss, there is a possible out of bounds write due to a missing bounds check. This could lead to local denial of service with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS11309816; Issue ID: MSV-10731.
What to do
Check whether your setup matches what the bug needs.
Affects the listed MediaTek chipsets (MT2735, MT2737, MT6880, MT6890, MT6980D, MT6982, MT6986, MT6988, MT6990) in the gnss subcomponent.Workaround: No fix is listed in the checked facts, so no workaround is documented. Limiting use of the GNSS feature is the only option the facts support, and the device maker or MediaTek should be asked for interim guidance.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- MediaTek, Inc. MediaTek chipset
MT2735, MT2737, MT6880, MT6890, MT6980D, MT6982, MT6986, MT6988, MT6990
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-20550
What does this mean?
The GNSS (satellite positioning) component on the listed MediaTek chipsets is missing a bounds check, so it can write data outside the memory area it should stay within (an out-of-bounds write, CWE-787).Source: mediatek.com
Am I affected, and how do I check?
The advisory lists MediaTek chipsets MT2735, MT2737, MT6880, MT6890, MT6980D, MT6982, MT6986, MT6988 and MT6990 in the gnss subcomponent. To check a device, look up its chipset model in the device or board specifications; the facts give no version numbers or settings to compare.Source: mediatek.com
What should I do about it?
The facts do not name a fixed firmware or patch level, so no specific upgrade target can be given. Install the latest security update from the device maker and check the MediaTek advisory for the patched version.Source: mediatek.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
No fix is listed in the checked facts, so no workaround is documented. Limiting use of the GNSS feature is the only option the facts support, and the device maker or MediaTek should be asked for interim guidance.Source: mediatek.com