{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-30814 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-30814 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-30814 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. AX53 v1.0, published on 8 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-30814 and fix it if it is affected.\n\nWhat it is: CVE-2026-30814 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. AX53 v1.0, published on 8 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-30814 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. AX53 v1.0. 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-30814/ (Markdown: https://insights.sbomify.com/CVE-2026-30814/index.md)","id":"CVE-2026-30814","markdown":"https://insights.sbomify.com/CVE-2026-30814/index.md","name":"CVE-2026-30814","record":{"aliases":["GHSA-w4qp-mpq3-cw45"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link router","requires_auth":"high_privilege","summary":"An authenticated adjacent attacker can trigger a stack-based buffer overflow in TP-Link Archer AX53 routers, potentially executing arbitrary code or causing a crash.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"archer_ax53_firmware","vendor":"tp-link"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow in the tmpServer module of TP-Link Archer AX53 v1.0 allows an authenticated adjacent attacker to trigger a segmentation fault and potentially execute arbitrary code via a specially crafted configuration file. Successful exploitation may cause a crash and could allow arbitrary code execution, enabling modification of device state, exposure of sensitive data, or further compromise of device integrity.\n\nThis issue affects AX53 v1.0: before 1.7.1 Build 20260213.","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":"Buffer Overflow Vulnerability in TP-Link AX53","id":"CVE-2026-30814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"OS Command Injection Vulnerability in OpenVPN Module in TP-Link AX53","id":"CVE-2026-30815"},"packages":[],"prev":{"headline":"SQL Injection in Module Search leads to Database Compromise","id":"CVE-2026-30813"},"products":["AX53 v1.0"],"published":"2026-04-08","related":[{"cvss_score":8.6,"headline":"Heap-based Buffer Overflow Vulnerability in Archer AX53 and AX12","id":"CVE-2025-62673","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.5,"headline":"OS Command Injection Vulnerability in OpenVPN Module in TP-Link AX53","id":"CVE-2026-30815","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":8.5,"headline":"OS Command Injection Vulnerability in dnsmasq Module in TP-Link AX53","id":"CVE-2026-30818","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":7.7,"headline":"Buffer Overflow in Network Probe Handling Function of TP-Link Archer AX53 + Archer AX55","id":"CVE-2025-15608","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.3,"headline":"Authenticated Command Injection in mcsd Service of TP-Link Archer AX53","id":"CVE-2025-15607","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":7.3,"headline":"Heap-based Buffer Overflow Vulnerability in TP-Link Archer AX53","id":"CVE-2025-58077","kev_date_added":null,"published":"2026-02-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":"total"},"state":"PUBLISHED","updated":"2026-05-07","vendors":["TP-Link Systems Inc."]},"summary":"An authenticated adjacent attacker can trigger a stack-based buffer overflow in TP-Link Archer AX53 routers, potentially executing arbitrary code or causing a crash.","url":"https://insights.sbomify.com/CVE-2026-30814/"}