Is CVE-2026-57879 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57879 being exploited in the wild.

How severe is CVE-2026-57879?

Critical severity, with a CVSS score of 9.8, published 26 June 2026.

Which products and versions are affected?

Geovision Gv-Lpc2011 V1.12 and earlier; Geovision Gv-Lpc2211 V1.12 and earlier.

Is there a fix for CVE-2026-57879?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-57879 attacked?

It is attacked over the network, in device firmware.

Am I affected by CVE-2026-57879?

Check whether you run Geovision Gv-Lpc2011 or Geovision Gv-Lpc2211 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57879: GeoVision GV-LPC series stack-based buffer overflow in ssvr

CVE-2026-57879 · Severity: critical · CVSS 9.8 · Published 2026-06-26

A critical security vulnerability exists in GeoVision license plate recognition cameras. An attacker can remotely exploit this flaw without a password to crash the device or potentially take full control of the camera. This could lead to a complete loss of video surveillance, unauthorized access to sensitive visual data, or the device being used as a foothold to attack other parts of the corporate network.

Technologies: Geovision Gv-Lpc2011, Geovision Gv-Lpc2211. Vendors: Geovision.

Quick answers

Is CVE-2026-57879 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57879 being exploited in the wild.
How severe is CVE-2026-57879?: Critical severity, with a CVSS score of 9.8, published 26 June 2026.
Which products and versions are affected?: Geovision Gv-Lpc2011 V1.12 and earlier; Geovision Gv-Lpc2211 V1.12 and earlier.
Is there a fix for CVE-2026-57879?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-57879 attacked?: It is attacked over the network, in device firmware.
Am I affected by CVE-2026-57879?: Check whether you run Geovision Gv-Lpc2011 or Geovision Gv-Lpc2211 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A stack-based buffer overflow (CWE-121) exists in the 'ssvr' service of GeoVision GV-LPC2011 and GV-LPC2211 devices running firmware V1.12 and earlier. The vulnerability is triggered by insufficient bounds checking when the service processes custom authentication data within Real Time Streaming Protocol (RTSP) requests. A remote, unauthenticated attacker can exploit this by sending a specially crafted RTSP request to the device. Successful exploitation can lead to memory corruption, denial of service (DoS), or arbitrary code execution with the privileges of the ssvr process. GeoVision has released firmware version 1.13 to address this issue.

Affected products

GeoVision GV-LPC2011 V1.12 and earlier
GeoVision GV-LPC2211 V1.12 and earlier

Timeline

2026-06-26: disclosed
2026-06-26: advisory

References

https://www.geovision.com.tw/cyber_security.php

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.