In Modem, there is a possible out of bounds write due to improper input validation.
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
- Not reported
Do first: Workaround: The checked facts do not list a workaround or mitigation. Until a fix is available, no specific steps can be confirmed from these sources.
- 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? →
- 24/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? →
- Unclear
- 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: yes
- Technical impact: total
Summary
The affected software is the modem firmware in certain mobile devices. An attacker operating a rogue base station could exploit an out-of-bounds write flaw to gain elevated privileges on a connected device without user interaction.
Read the original description
In Modem, there is a possible out of bounds write due to improper input validation. This could lead to remote escalation of privilege, 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: MOLY01775865; Issue ID: MSV-8895.
What to do
Workaround: The checked facts do not list a workaround or mitigation. Until a fix is available, no specific steps can be confirmed from these sources.
Timeline
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- CVE published
- First seen by cve.now1 day
- Record last updated
Affected versions
- MediaTek, Inc. MediaTek chipset
MT2716, MT2735, MT2737, MT6739, MT6761, MT6762, MT6763, MT6765, MT6767, MT6768, MT6769, MT6771, MT6779, MT6781, MT6783, MT6785, MT6789, MT6833, MT6835, MT6853, MT6855, MT6858, MT6873, MT6875, MT6877, MT6878, MT6879, MT6880, MT6881, MT6883, and 45 more
Evidence 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-20549
What does this mean?
The Modem component can write data outside the memory area it is meant to use. This happens because it does not properly check input before using it.Source: mediatek.com
Am I affected, and how do I check?
The issue is listed for the Modem subcomponent on MediaTek chipsets, with examples including MT2716, MT6739, MT6789, and MT8893. The checked facts give no affected version ranges, so check the chipset model in your device's specifications to see whether it appears in the list.Source: mediatek.com
What should I do about it?
The checked facts do not name a fixed version or an upgrade target. Check with the device maker for a firmware or security update that addresses CVE-2026-20549.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?
The checked facts do not list a workaround or mitigation. Until a fix is available, no specific steps can be confirmed from these sources.Source: mediatek.com