{"answers":{"affected":"It affects 5 products.","exploited":"There is no known exploitation of CVE-2026-20491 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20491 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20491 is a medium-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-20491 and fix it if it is affected.\n\nWhat it is: CVE-2026-20491 is a medium-severity memory corruption vulnerability in MediaTek, Inc. MediaTek chipset, published on 3 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-20491 in the wild and no public exploit code.\n\nAffected product: MediaTek, Inc. MediaTek chipset. 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-2026-20491/ (Markdown: https://insights.sbomify.com/CVE-2026-20491/index.md)","id":"CVE-2026-20491","markdown":"https://insights.sbomify.com/CVE-2026-20491/index.md","name":"CVE-2026-20491","record":{"aliases":["GHSA-639g-9ffj-23fc"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MediaTek chipset firmware","requires_auth":"low_privilege","summary":"A local attacker can cause a denial of service via an out-of-bounds write in MediaTek chipset firmware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"MediaTek","cpe":[{"product":"mt2735_firmware","vendor":"mediatek"},{"product":"mt2737_firmware","vendor":"mediatek"},{"product":"mt6890_firmware","vendor":"mediatek"},{"product":"mt6988_firmware","vendor":"mediatek"},{"product":"mt6990_firmware","vendor":"mediatek"}],"cvss":{"score":5.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In med, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local denial of service with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS10981478 (Note: For MT6890, MT6990, MT6988) / AUTO00851173 (Note: For MT2735, MT2737); Issue ID: MSV-7652.","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 MediaTek chipset","id":"CVE-2026-20491","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Race condition in MediaTek chipset","id":"CVE-2026-20492"},"packages":[],"prev":{"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20490"},"products":["MediaTek chipset"],"published":"2026-08-03","related":[{"cvss_score":8.8,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20433","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":8,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20432","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":7.5,"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20479","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":6.7,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20528","kev_date_added":null,"published":"2026-10-05"},{"cvss_score":6.5,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20449","kev_date_added":null,"published":"2026-05-04"},{"cvss_score":6.5,"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20450","kev_date_added":null,"published":"2026-05-04"},{"cvss_score":6.5,"headline":"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","id":"CVE-2025-20659","kev_date_added":null,"published":"2025-04-07"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["MediaTek, Inc."]},"summary":"A local attacker can cause a denial of service via an out-of-bounds write in MediaTek chipset firmware.","url":"https://insights.sbomify.com/CVE-2026-20491/"}