{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-35716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35716 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 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-35716 and fix it if it is affected.\n\nWhat it is: CVE-2026-35716 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35716 in the wild and no public exploit code.\n\nAffected product: n/a. 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-35716/ (Markdown: https://insights.sbomify.com/CVE-2026-35716/index.md)","id":"CVE-2026-35716","markdown":"https://insights.sbomify.com/CVE-2026-35716/index.md","name":"CVE-2026-35716","record":{"aliases":["GHSA-pj36-9w4r-h2r4"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"VIVOTEK IP camera","requires_auth":"low_privilege","summary":"Authenticated attackers can execute arbitrary code as root via a stack buffer overflow in VIVOTEK camera firmware.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fd8136_firmware","vendor":"vivotek"}],"cvss":{"score":6.3,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack-based buffer overflow in the motion_privacy.cgi binary in VIVOTEK FD8136 firmware FD8136-VVTK-0300a allows authenticated remote attackers to execute arbitrary code as root via an oversized n1 parameter in a POST request to the /cgi-bin/admin/setpm.cgi, /cgi-bin/admin/setmd.cgi, or /cgi-bin/admin/setmd_profile.cgi endpoint (all symlinks to the same binary). The parameter value is copied into a fixed-size 0xa4-byte stack buffer without bounds checking, overwriting the saved link register. The binary is compiled without stack canaries.","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 n/a","id":"CVE-2026-35716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2026-35717"},"packages":[],"prev":{"headline":"Anviz CX2 Lite Command Injection","id":"CVE-2026-35682"},"products":["n/a"],"published":"2026-06-02","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-14494","kev_date_added":null,"published":"2019-07-10"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-14495","kev_date_added":null,"published":"2019-07-10"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14496","kev_date_added":null,"published":"2019-07-10"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2026-30650","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2026-30652","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.3,"headline":"Memory corruption in n/a","id":"CVE-2026-30649","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2026-35718","kev_date_added":null,"published":"2026-06-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":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Authenticated attackers can execute arbitrary code as root via a stack buffer overflow in VIVOTEK camera firmware.","url":"https://insights.sbomify.com/CVE-2026-35716/"}