CVE-2026-1457

CVE-2026-1457 is a high-severity vulnerability in Tp-link Vigi C385 Firmware with a CVSS 3.x base score of 8.8. 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

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.

Frequently asked questions

What is CVE-2026-1457?
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.
How severe is CVE-2026-1457?
CVE-2026-1457 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-1457 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 7% (93rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-1457?
CVE-2026-1457 affects Tp-link Vigi C385 Firmware. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-1457?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-1457 have an EU (EUVD) identifier?
Yes. CVE-2026-1457 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-4967.
When was CVE-2026-1457 published?
CVE-2026-1457 was published on 2026-01-29 and last updated on 2026-06-17.

References

Affected products (1)

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

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