Quick answers
- Is CVE-2026-57877 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57877 being exploited in the wild.
- How severe is CVE-2026-57877?
- High severity, with a CVSS score of 8.6, 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-57877?
- 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-57877 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-57877?
- 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
An unauthenticated format string vulnerability (CWE-134) exists in the 'vlsvr' service of GeoVision GV-LPC2011 and GV-LPC2211 devices running firmware version 1.12 and earlier. The flaw is located within the login processing path, where externally controlled input is improperly handled during log message formatting. A remote, unauthenticated attacker can exploit this by sending crafted login data. Successful exploitation can result in information disclosure, memory corruption, or a denial of service (DoS) condition. The vulnerability is addressed in firmware version 1.13.
Affected products
- GeoVision GV-LPC2011 v1.12 and earlier
- GeoVision GV-LPC2211 v1.12 and earlier
Timeline
- 2026-06-26: advisory: NVD publication date
- 2026-06-26: disclosed: CVE published by GeoVision (CNA)