CVE-2026-1457

Unknown Unknown - Not Provided

Authenticated Buffer Overflow in TP-Link VIGI C385 Web API Enables RCE

Publication date: 2026-01-29

Last updated on: 2026-03-09

Assigner: TPLink

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-29

Last Modified

2026-03-09

Generated

2026-07-06

AI Q&A

2026-01-29

EPSS Evaluated

2026-07-05

NVD

CVE-2026-1457

EUVD

EUVD-2026-4967

Affected Vendors & Products

Vendor	Product	Version / Range
tp-link	vigi_c385_firmware	to 3.1.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-121	A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

Executive Summary

This vulnerability is an authenticated buffer handling flaw in the TP-Link VIGI C385 V1 Web API. Due to lack of proper input sanitization, an authenticated attacker can trigger a buffer overflow, causing memory corruption. This may allow the attacker to execute arbitrary code with elevated privileges on the device. [2]

Impact Analysis

If exploited, this vulnerability can allow an authenticated attacker to execute arbitrary code with elevated privileges on the affected TP-Link VIGI C385 V1 device. This could lead to full compromise of the device, potentially allowing the attacker to control it remotely and perform unauthorized actions. [2]

Mitigation Strategies

To mitigate this vulnerability, update the TP-Link VIGI C385 V1 device firmware to the latest version available, specifically to version 3.1.1 Build 251124 Rel.50371n or later, as recommended by TP-Link. Applying this update will remediate the buffer handling flaw and prevent exploitation. [2]

Hi! I’m here to help you understand CVE-2026-1457. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70