{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18607 exists.","fix":"No fix has been published for CVE-2026-18607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-18607 is a high-severity memory corruption vulnerability in Wavlink NU516, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-18607 and fix it if it is affected.\n\nWhat it is: CVE-2026-18607 is a high-severity memory corruption vulnerability in Wavlink NU516, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18607 exists.\n\nAffected product: Wavlink NU516. 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-18607/ (Markdown: https://insights.sbomify.com/CVE-2026-18607/index.md)","id":"CVE-2026-18607","markdown":"https://insights.sbomify.com/CVE-2026-18607/index.md","name":"CVE-2026-18607","record":{"aliases":["GHSA-82rw-j2xw-2766"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Wavlink router","requires_auth":"low_privilege","summary":"Remote attackers can trigger a stack-based buffer overflow in the lighttpd upload.cgi component via the HTTP_COOKIE argument, potentially leading to code execution on Wavlink routers.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"A security vulnerability has been detected in Wavlink WN572, WN570H, WN573, WN529, WN530, WN531, WN535, etc. WN529, WN530, WN531, WN535, WN536, WN551, WN557 and NU516 up to 20260609. Affected by this issue is the function strcpy of the file upload.cgi of the component lighttpd. The manipulation of the argument HTTP_COOKIE leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Wavlink NU516 lighttpd upload.cgi strcpy stack-based overflow","id":"CVE-2026-18607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Privilege escalation in Red Hat OpenShift AI 2.25","id":"CVE-2026-18608"},"packages":[],"prev":{"headline":"Razer RzUpdateService Named Pipe RzUpdateService.exe privileges management","id":"CVE-2026-18606"},"products":["NU516","WN529","WN530","WN531","WN535","WN536","WN551","WN557","WN570H","WN572","WN573","etc. WN529"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-03","vendors":["Wavlink"]},"summary":"Remote attackers can trigger a stack-based buffer overflow in the lighttpd upload.cgi component via the HTTP_COOKIE argument, potentially leading to code execution on Wavlink routers.","url":"https://insights.sbomify.com/CVE-2026-18607/"}