CVE-2026-35717
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA stack-based buffer overflow in the export_language.cgi binary in VIVOTEK FD8136 firmware FD8136-VVTK-0300a allows authenticated remote attackers to execute arbitrary code as root via a crafted POST request to the /cgi-bin/admin/export_language.cgi endpoint. The handler passes the attacker-controlled Content-Length value directly to fread() as the read size into a fixed-size 0x60-byte stack buffer, overwriting the saved link register. The binary is compiled without stack canaries.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStack-based buffer overflow in VIVOTEK FD8136 firmware's export_language.cgi binary. The CGI handler passes the attacker-controlled Content-Length header value directly to fread() as the size parameter into a fixed 0x60-byte (96 bytes) stack buffer without bounds checking, allowing overwriting of the saved link register. The binary is compiled without stack canaries, enabling arbitrary code execution as root.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0300aCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the camera's web interface or check the device label/metadata to confirm it is a Vivotek FD8136 camera model.Affected if The device is not a Vivotek FD8136 model.
-
Check the firmware versionLog into the camera web interface and navigate to Setup > System > Maintenance or similar, or use the CGI API to query the firmware version. Compare the installed firmware version to 0300a.Affected if The installed firmware version equals 0300a.
-
Verify the export_language.cgi endpoint is accessibleAttempt to access the export_language.cgi endpoint via HTTP/HTTPS (e.g., GET /cgi-bin/export_language.cgi). A response (even an error) indicates the endpoint exists and is reachable.Affected if The endpoint responds and the camera is reachable on the network.
-
Confirm web authentication is configuredCheck whether the camera's web interface requires authentication. The vulnerability requires an authenticated session to exploit, so verify if valid credentials can be obtained or if authentication is enabled in the system settings.Affected if Web authentication is enabled and valid credentials exist or can be obtained.
A user is affected if they have a Vivotek FD8136 camera running firmware version 0300a with the web interface and export_language.cgi endpoint accessible, regardless of whether authentication is enabled (since the check covers obtaining valid credentials).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataIsolate the device on a restricted network segment to limit administrative interface exposure. If possible, disable or remove the affected CGI endpoint. Contact VIVOTEK for firmware updates; if unavailable, consider device replacement.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35717 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-35717 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data