{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-20680 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20680 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20680 is a critical memory corruption vulnerability in MediaTek, Inc. MT7902, MT7920, MT7921, MT7922, MT7925, MT7927, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-20680 and fix it if it is affected.\n\nWhat it is: CVE-2025-20680 is a critical memory corruption vulnerability in MediaTek, Inc. MT7902, MT7920, MT7921, MT7922, MT7925, MT7927, published on 8 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-20680 in the wild and no public exploit code.\n\nAffected product: MediaTek, Inc. MT7902, MT7920, MT7921, MT7922, MT7925, MT7927. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-20680/ (Markdown: https://insights.sbomify.com/CVE-2025-20680/index.md)","id":"CVE-2025-20680","markdown":"https://insights.sbomify.com/CVE-2025-20680/index.md","name":"CVE-2025-20680","record":{"aliases":["GHSA-8744-rghf-gq4r"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"MediaTek Bluetooth driver","requires_auth":"none","summary":"A local attacker can escalate privileges via an out-of-bounds write in the MediaTek Bluetooth driver, requiring user execution privileges but no interaction.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"MediaTek","cpe":[{"product":"nbiot_sdk","vendor":"mediatek"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"In Bluetooth driver, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00418044; Issue ID: MSV-3482.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in MT7902, MT7920, MT7921, MT7922, MT7925, MT7927","id":"CVE-2025-20680","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in MT6890, MT7615, MT7622, MT7663, MT7915","id":"CVE-2025-20681"},"packages":[],"prev":{"headline":"Denial of service in 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, MT6983, MT6983T, MT6985, MT6985T, MT6989, MT6989T, MT6990, MT6991, MT8666, MT8667, MT8673, MT8675, MT8676, MT8678, MT8765, MT8766, MT8766R, MT8768, MT8771, MT8781, MT8786, MT8788, MT8788E, MT8789, MT8791, MT8791T, MT8795T, MT8797, MT8798, MT8863, MT8873, MT8883, MT8893","id":"CVE-2025-20678"},"products":["MT7902, MT7920, MT7921, MT7922, MT7925, MT7927"],"published":"2025-07-08","related":[{"cvss_score":9.8,"headline":"Memory corruption in MT2621, MT2625","id":"CVE-2022-26437","kev_date_added":null,"published":"2022-08-01"},{"cvss_score":9.3,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20407","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":7.8,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20423","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":6.7,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20436","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":6.5,"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20419","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":5.5,"headline":"Denial of service in MT7902, MT7920, MT7921, MT7922, MT7925, MT7927","id":"CVE-2025-20687","kev_date_added":null,"published":"2025-07-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["MediaTek, Inc."]},"summary":"A local attacker can escalate privileges via an out-of-bounds write in the MediaTek Bluetooth driver, requiring user execution privileges but no interaction.","url":"https://insights.sbomify.com/CVE-2025-20680/"}