# CVE-2026-1457: Authenticated RCE Vulnerability Due to Buffer Overflow on TP-Link VIGI C385

> Authenticated attackers can trigger a buffer overflow in the web API to execute arbitrary code with elevated privileges on TP-Link VIGI cameras.

- **Severity:** High 8.5 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-j5cc-hmp5-4pfq

## What is CVE-2026-1457?

CVE-2026-1457 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. VIGI C485 V1, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An authenticated buffer handling flaw in TP-Link VIGI C385 V1 Web API lacking input sanitization, may allow memory corruption leading to remote code execution. Authenticated attackers may trigger buffer overflow and potentially execute arbitrary code with elevated privileges.

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

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

It affects 1 product.


Products: Tp-Link Vigi C385 Firmware.

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

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

## Is CVE-2026-1457 being exploited?

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

Public exploit code:

- CVE-2026-1457 is an authenticated buffer overflow vulnerability in the web API of TP-Link VIGI C385 V1. This vulnerability allows authenticated attackers to perform remote code execution (RCE). (github_poc): https://github.com/ii4gsp/CVE-2026-1457

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1457 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. VIGI C485 V1, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1457 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. VIGI C485 V1. 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-1457/ (Markdown: https://insights.sbomify.com/CVE-2026-1457/index.md)
```

## Sources

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

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