How severe is CVE-2026-35716?

CVE-2026-35716 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.

Is CVE-2026-35716 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-35716?

CVE-2026-35716 affects Vivotek Fd8136 Firmware. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-35716?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-35716 have an EU (EUVD) identifier?

Yes. CVE-2026-35716 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-33969.

When was CVE-2026-35716 published?

CVE-2026-35716 was published on 2026-06-02 and last updated on 2026-07-05.

CVE-2026-35716

CVE-2026-35716 is a medium-severity vulnerability in Vivotek Fd8136 Firmware with a CVSS 3.x base score of 6.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-121.

Key facts

Severity: Medium (CVSS 3.x base score 6.3)
EPSS exploit prediction: 0% (24th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-33969
Weakness: CWE-121
Affected product: Vivotek Fd8136 Firmware
Published: 2026-06-02
Last modified: 2026-07-05

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.

Frequently asked questions

What is CVE-2026-35716?: 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.
How severe is CVE-2026-35716?: CVE-2026-35716 has a CVSS 3.x base score of 6.3, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity low, and availability low.
Is CVE-2026-35716 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (24th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-35716?: CVE-2026-35716 affects Vivotek Fd8136 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-35716?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-35716 have an EU (EUVD) identifier?: Yes. CVE-2026-35716 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-33969.
When was CVE-2026-35716 published?: CVE-2026-35716 was published on 2026-06-02 and last updated on 2026-07-05.

References

https://github.com/xchg-rax-rax/vulnerability-research/tree/main/CVE-2026-35716

EU advisories (EUVD)

http://vivotek.com

Affected products (1)

cpe:2.3:o:vivotek:fd8136_firmware:0300a:*:*:*:*:*:*:*

More vulnerabilities in Vivotek Fd8136 Firmware

CVE-2018-14496 — Critical (CVSS 9.8): Vivotek FD8136 devices allow remote memory corruption and remote code execution because of a stack-based buffer…
CVE-2018-14495 — Critical (CVSS 9.8): Vivotek FD8136 devices allow Remote Command Injection, aka "another command injection vulnerability in our target…
CVE-2018-14494 — Critical (CVSS 9.8): Vivotek FD8136 devices allow Remote Command Injection, related to BusyBox and wget. NOTE: the vendor sent a…
CVE-2026-30652 — High (CVSS 8.8): A remote buffer overflow vulnerability exists in the /cgi-bin/dido/setdo.cgi endpoint of the admin interface of Vivotek…
CVE-2026-30650 — High (CVSS 8.8): A post-authentication remote buffer overflow vulnerability exists in the /cgi-bin/admin/eventtask.cgi endpoint of the…
CVE-2026-30649 — High (CVSS 7.3): Buffer Overflow vulnerability in VIVOTEK INC FD8136-VVTK-0300a allows a remote attacker to execute arbitrary code via…

All CVEs affecting Vivotek Fd8136 Firmware →

Other CWE-121 (Stack-based Buffer Overflow) vulnerabilities

CVE-2026-12848 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12847 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12846 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-12485 — Critical (CVSS 10.0): GV-I/O Box 4E is a smart embedded device with 4 input and 4 relays output that can be controlled over Ethernet and…
CVE-2026-37541 — Critical (CVSS 10.0): Buffer overflow vulnerability in Open Vehicle Monitoring System 3 (OVMS3) 3.3.005. In canformat_gvret.cpp, the length…
CVE-2026-42996 — Critical (CVSS 10.0): JS8Call through 2.3.1 and JS8Call-improved before 3.0 have a stack-based buffer overflow via a radio transmission of…

Browse all CWE-121 (Stack-based Buffer Overflow) vulnerabilities →