{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-22220 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-22220 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-22220 is a medium-severity denial of service vulnerability in TP-Link Systems Inc. Archer BE230 v1.2, published on 3 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-22220 and fix it if it is affected.\n\nWhat it is: CVE-2026-22220 is a medium-severity denial of service vulnerability in TP-Link Systems Inc. Archer BE230 v1.2, published on 3 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-22220 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Archer BE230 v1.2. 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-22220/ (Markdown: https://insights.sbomify.com/CVE-2026-22220/index.md)","id":"CVE-2026-22220","markdown":"https://insights.sbomify.com/CVE-2026-22220/index.md","name":"CVE-2026-22220","record":{"aliases":["GHSA-gm7f-mr33-3p7w"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Wi-Fi router","requires_auth":"high_privilege","summary":"A network-adjacent attacker with high privileges can cause the TP-Link Archer BE230 web interface to become unresponsive via improper input validation.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"archer_be230_firmware","vendor":"tp-link"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A lack of proper input validation in the HTTP processing path in TP-Link Archer BE230 v1.2 (web modules) may allow a crafted request to cause the device’s web service to become unresponsive, resulting in a denial of service condition. A network adjacent attacker with high privileges could cause the device’s web interface to temporarily stop responding until it recovers or is rebooted.\nThis issue affects Archer BE230 v1.2 \u003c 1.2.4 Build 20251218 rel.70420.","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":"Improper Input Validation Leading to DoS on TP-Link Archer BE230","id":"CVE-2026-22220","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1","id":"CVE-2026-22221"},"packages":[],"prev":{"headline":"Chainlit \u003c 2.9.4 SQLAlchemy Data Layer SSRF via /project/element","id":"CVE-2026-22219"},"products":["Archer BE230 v1.2"],"published":"2026-02-03","related":[{"cvss_score":8.6,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and Deco BE25 v1.0","id":"CVE-2026-22229","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and AXE75 v1.0","id":"CVE-2026-0630","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Authenticated Command Injection Vulnerability in Surfshark VPN Login in multiple Archer products","id":"CVE-2026-0631","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1","id":"CVE-2026-22221","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and AXE75 v2","id":"CVE-2026-22222","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2 and BE3600 v1","id":"CVE-2026-22223","kev_date_added":null,"published":"2026-02-02"},{"cvss_score":8.5,"headline":"Command Injection Vulnerability on TP-Link Archer BE230 v1.2","id":"CVE-2026-22224","kev_date_added":null,"published":"2026-02-02"}],"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-02-04","vendors":["TP-Link Systems Inc."]},"summary":"A network-adjacent attacker with high privileges can cause the TP-Link Archer BE230 web interface to become unresponsive via improper input validation.","url":"https://insights.sbomify.com/CVE-2026-22220/"}