{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2026-20408 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20408 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20408 is a high-severity memory corruption vulnerability in Mediatek Software Development Kit, published on 2 Feb 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-20408 and fix it if it is affected.\n\nWhat it is: CVE-2026-20408 is a high-severity memory corruption vulnerability in Mediatek Software Development Kit, published on 2 Feb 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-20408 in the wild and no public exploit code.\n\nAffected product: Mediatek Software Development Kit. 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-20408/ (Markdown: https://insights.sbomify.com/CVE-2026-20408/index.md)","id":"CVE-2026-20408","markdown":"https://insights.sbomify.com/CVE-2026-20408/index.md","name":"CVE-2026-20408","record":{"aliases":["GHSA-h372-rxq3-5q6p"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MediaTek chipset","requires_auth":"none","summary":"A heap buffer overflow in MediaTek chipsets allows remote attackers to escalate privileges without user interaction.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"MediaTek","cpe":[{"product":"software_development_kit","vendor":"mediatek"},{"product":"openwrt","vendor":"openwrt"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"In wlan, there is a possible out of bounds write due to a heap buffer overflow. This could lead to remote (proximal/adjacent) escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00461651; Issue ID: MSV-4758.","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-20408","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"mediatek:software_development_kit","products":["mediatek:software_development_kit","openwrt:openwrt"],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20409"},"packages":[],"prev":{"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20407"},"products":["MediaTek chipset"],"published":"2026-02-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in MT6890, MT7615, MT7622, MT7663, MT7915","id":"CVE-2025-20681","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"Memory corruption in MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986","id":"CVE-2025-20682","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"Memory corruption in MT6890, MT7615, MT7622, MT7663, MT7915, MT7916, MT7981, MT7986","id":"CVE-2025-20683","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"Memory corruption in MT7615, MT7622, MT7663","id":"CVE-2025-20684","kev_date_added":null,"published":"2025-07-08"},{"cvss_score":9.8,"headline":"Missing authorization in MT6890, MT6990, MT7915, MT7916, MT7981, MT7986, MT7990, MT7992, MT7993","id":"CVE-2025-20674","kev_date_added":null,"published":"2025-06-02"},{"cvss_score":9.8,"headline":"Memory corruption in MT6890, MT7915, MT7916, MT7981, MT7986","id":"CVE-2025-20646","kev_date_added":null,"published":"2025-03-03"},{"cvss_score":9.8,"headline":"Memory corruption in MT6890, MT7915, MT7916, MT7981, MT7986","id":"CVE-2024-20017","kev_date_added":null,"published":"2024-03-04"}],"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-03-30","vendors":["MediaTek, Inc."]},"summary":"A heap buffer overflow in MediaTek chipsets allows remote attackers to escalate privileges without user interaction.","url":"https://insights.sbomify.com/CVE-2026-20408/"}