{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-20446 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-20446 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-20446 is a medium-severity vulnerability in MediaTek, Inc. MediaTek chipset, published on 7 Apr 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-20446 and fix it if it is affected.\n\nWhat it is: CVE-2026-20446 is a medium-severity vulnerability in MediaTek, Inc. MediaTek chipset, published on 7 Apr 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-20446 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-20446/ (Markdown: https://insights.sbomify.com/CVE-2026-20446/index.md)","id":"CVE-2026-20446","markdown":"https://insights.sbomify.com/CVE-2026-20446/index.md","name":"CVE-2026-20446","record":{"aliases":["GHSA-xv4p-823r-9vr8"],"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":"An integer overflow in MediaTek chipset secure boot allows local attackers with physical access to cause a denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"MediaTek","cpe":[{"product":"mt6813_firmware","vendor":"mediatek"}],"cvss":{"score":4.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-190","name":"Integer Overflow or Wraparound"},{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"In sec boot, there is a possible out of bounds write due to an integer overflow. This could lead to local denial of service, if an attacker has physical access to the device, with User execution privileges needed. User interaction is not needed for exploitation. Patch ID: ALPS09963054; Issue ID: MSV-3899.","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":"Integer overflow in MediaTek chipset","id":"CVE-2026-20446","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20447"},"packages":[],"prev":{"headline":"Race condition in MediaTek chipset","id":"CVE-2026-20445"},"products":["MediaTek chipset"],"published":"2026-04-07","related":[{"cvss_score":6.5,"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20431","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":5.5,"headline":"Memory corruption in MediaTek chipset","id":"CVE-2026-20476","kev_date_added":null,"published":"2026-08-03"},{"cvss_score":4.4,"headline":"Denial of service in MediaTek chipset","id":"CVE-2026-20490","kev_date_added":null,"published":"2026-08-03"}],"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-04-07","vendors":["MediaTek, Inc."]},"summary":"An integer overflow in MediaTek chipset secure boot allows local attackers with physical access to cause a denial of service.","url":"https://insights.sbomify.com/CVE-2026-20446/"}