# CVE-2025-20659: Denial of service in MT2735, MT2737, MT6739, MT6761, MT6762, MT6762D, MT6762M, MT6763, MT6765, MT6765T, MT6767, MT6768, MT6769, MT6769K, MT6769S, MT6769T, MT6769Z, MT6771, MT6779, MT6781, MT6783, MT6785, MT6785T, MT6785U, MT6789, MT6813, MT6833, MT6833P, MT6835, MT6835T, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6878, MT6878M, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8791T, MT8796, MT8797, MT8798, MT8863 > A remote attacker can cause a system crash in MediaTek modem firmware by connecting a device to a rogue base station, requiring no user interaction. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 7 Apr 2025 - **Updated:** 17 Feb 2026 - **Also known as:** GHSA-8359-6xxw-qm22 ## What is CVE-2025-20659? CVE-2025-20659 is a medium-severity denial of service vulnerability in MediaTek, Inc. MT2735, MT2737, MT6739, MT6761, MT6762, MT6762D, MT6762M, MT6763, MT6765, MT6765T, MT6767, MT6768, MT6769, MT6769K, MT6769S, MT6769T, MT6769Z, MT6771, MT6779, MT6781, MT6783, MT6785, MT6785T, MT6785U, MT6789, MT6813, MT6833, MT6833P, MT6835, MT6835T, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6878, MT6878M, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8791T, MT8796, MT8797, MT8798, MT8863, published on 7 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description In Modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service, 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: MOLY01519028; Issue ID: MSV-2768. Weakness: CWE-125 (Out-of-bounds Read) ## Which versions are affected by CVE-2025-20659? It affects 85 products. Products: Mediatek Mt2735 Firmware, Mediatek Mt2737 Firmware, Mediatek Mt6739 Firmware, Mediatek Mt6761 Firmware, Mediatek Mt6762 Firmware, Mediatek Mt6762d Firmware, Mediatek Mt6762m Firmware, Mediatek Mt6763 Firmware, Mediatek Mt6765 Firmware, Mediatek Mt6765t Firmware, Mediatek Mt6767 Firmware, Mediatek Mt6768 Firmware, Mediatek Mt6769 Firmware, Mediatek Mt6769k Firmware, Mediatek Mt6769s Firmware, Mediatek Mt6769t Firmware, Mediatek Mt6769z Firmware, Mediatek Mt6771 Firmware, Mediatek Mt6779 Firmware, Mediatek Mt6781 Firmware and 65 more. ## How do I fix CVE-2025-20659? No fix has been published for CVE-2025-20659 yet. Limit exposure of the affected software until one is available. ## Is CVE-2025-20659 being exploited? There is no known exploitation of CVE-2025-20659 in the wild and no public exploit code. ## Other vulnerabilities in MediaTek, Inc. MT2735, MT2737, MT6739, MT6761, MT6762, MT6762D, MT6762M, MT6763, MT6765, MT6765T, MT6767, MT6768, MT6769, MT6769K, MT6769S, MT6769T, MT6769Z, MT6771, MT6779, MT6781, MT6783, MT6785, MT6785T, MT6785U, MT6789, MT6813, MT6833, MT6833P, MT6835, MT6835T, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6878, MT6878M, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8791T, MT8796, MT8797, MT8798, MT8863 - [CVE-2026-20433](https://insights.sbomify.com/CVE-2026-20433/): Memory corruption in MediaTek chipset (high 8.8) - [CVE-2026-20432](https://insights.sbomify.com/CVE-2026-20432/): Memory corruption in MediaTek chipset (high 8.0) - [CVE-2026-20479](https://insights.sbomify.com/CVE-2026-20479/): Denial of service in MediaTek chipset (high 7.5) - [CVE-2026-20528](https://insights.sbomify.com/CVE-2026-20528/): Memory corruption in MediaTek chipset (medium 6.7) - [CVE-2026-20449](https://insights.sbomify.com/CVE-2026-20449/): Memory corruption in MediaTek chipset (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-20659 and fix it if it is affected. What it is: CVE-2025-20659 is a medium-severity denial of service vulnerability in MediaTek, Inc. MT2735, MT2737, MT6739, MT6761, MT6762, MT6762D, MT6762M, MT6763, MT6765, MT6765T, MT6767, MT6768, MT6769, MT6769K, MT6769S, MT6769T, MT6769Z, MT6771, MT6779, MT6781, MT6783, MT6785, MT6785T, MT6785U, MT6789, MT6813, MT6833, MT6833P, MT6835, MT6835T, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6878, MT6878M, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8791T, MT8796, MT8797, MT8798, MT8863, published on 7 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-20659 in the wild and no public exploit code. Affected product: MediaTek, Inc. MT2735, MT2737, MT6739, MT6761, MT6762, MT6762D, MT6762M, MT6763, MT6765, MT6765T, MT6767, MT6768, MT6769, MT6769K, MT6769S, MT6769T, MT6769Z, MT6771, MT6779, MT6781, MT6783, MT6785, MT6785T, MT6785U, MT6789, MT6813, MT6833, MT6833P, MT6835, MT6835T, MT6853, MT6853T, MT6855, MT6855T, MT6873, MT6875, MT6875T, MT6877, MT6877T, MT6877TT, MT6878, MT6878M, MT6879, MT6880, MT6883, MT6885, MT6886, MT6889, MT6890, MT6891, MT6893, MT6895, MT6895TT, MT6896, MT6897, MT6899, MT6980, MT6980D, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8791T, MT8796, MT8797, MT8798, MT8863. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-20659/ (Markdown: https://insights.sbomify.com/CVE-2025-20659/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-20659 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-20659 - OSV: https://osv.dev/vulnerability/CVE-2025-20659 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-20659/ Summaries are generated and may contain mistakes; the official description above is the record.