Quick answers
- Is CVE-2026-57874 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57874 being exploited in the wild.
- How severe is CVE-2026-57874?
- High severity, with a CVSS score of 7.5, 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-57874?
- 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-57874 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-57874?
- 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 classic buffer overflow (CWE-120) exists in the IEEE8021x_upload.cgi component of GeoVision GV-LPC2011 and GV-LPC2211 firmware. The vulnerability is rooted in insufficient bounds checking when parsing filename values within multipart upload data. A remote, unauthenticated attacker can exploit this by sending a crafted HTTP POST request containing an overly long filename string. This results in memory corruption and a subsequent denial of service (DoS) of the device. The issue 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: Initial disclosure by GeoVision