# CVE-2026-35716: Memory corruption in n/a

> Authenticated attackers can execute arbitrary code as root via a stack buffer overflow in VIVOTEK camera firmware.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-pj36-9w4r-h2r4

## What is CVE-2026-35716?

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.

### Official 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.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-35716?

It affects 1 product.


Products: Vivotek Fd8136 Firmware.

## How do I fix CVE-2026-35716?

No fix has been published for CVE-2026-35716 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35716 being exploited?

There is no known exploitation of CVE-2026-35716 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-14494](https://insights.sbomify.com/CVE-2018-14494/): Command injection in n/a (critical 9.8)
- [CVE-2018-14495](https://insights.sbomify.com/CVE-2018-14495/): Command injection in n/a (critical 9.8)
- [CVE-2018-14496](https://insights.sbomify.com/CVE-2018-14496/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-30650](https://insights.sbomify.com/CVE-2026-30650/): Memory corruption in n/a (high 8.8)
- [CVE-2026-30652](https://insights.sbomify.com/CVE-2026-30652/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35716 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-35716 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35716/ (Markdown: https://insights.sbomify.com/CVE-2026-35716/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35716
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35716
- OSV: https://osv.dev/vulnerability/CVE-2026-35716

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35716/
Summaries are generated and may contain mistakes; the official description above is the record.