# CVE-2026-35718: Path traversal in n/a

> Authenticated attackers can read arbitrary files on VIVOTEK IP cameras via a path traversal vulnerability in the admin download endpoint.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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-rw3h-hf66-rvh4

## What is CVE-2026-35718?

CVE-2026-35718 is a medium-severity path traversal 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 path traversal vulnerability in the /admin/downloadMedias.cgi endpoint of VIVOTEK INC FD8136-VVTK firmware 0300a allows authenticated attackers to read any file on the device via sending a crafted request.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Vivotek Fd8136 Firmware.

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

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

## Is CVE-2026-35718 being exploited?

There is no known exploitation of CVE-2026-35718 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-35718 and fix it if it is affected.

What it is: CVE-2026-35718 is a medium-severity path traversal 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-35718 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-35718/ (Markdown: https://insights.sbomify.com/CVE-2026-35718/index.md)
```

## Sources

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

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