Is CVE-2026-57875 exploited in the wild?

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

How severe is CVE-2026-57875?

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-57875?

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-57875 attacked?

It is attacked over the network, in device firmware.

Am I affected by CVE-2026-57875?

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-57875: GeoVision GV-LPC series NULL pointer dereference in CGI components

CVE-2026-57875 · Severity: high · CVSS 7.5 · Published 2026-06-26

GeoVision license plate recognition cameras are affected by a security flaw that allows an unauthenticated attacker to crash the device remotely. By sending a specially crafted web request, an attacker can trigger a system failure, leading to a total loss of camera availability and surveillance capabilities. This could disrupt security operations and monitoring at facilities using these specific camera models.

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

Quick answers

Is CVE-2026-57875 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57875 being exploited in the wild.
How severe is CVE-2026-57875?: 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-57875?: 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-57875 attacked?: It is attacked over the network, in device firmware.
Am I affected by CVE-2026-57875?: 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 NULL pointer dereference vulnerability exists in the HTTP request parsing logic of multiple CGI components within GeoVision GV-LPC2011 and GV-LPC2211 firmware. The issue stems from improper validation of required HTTP request metadata before it is processed by the affected components. A remote, unauthenticated attacker can exploit this by sending a specially crafted HTTP request to the device. Successful exploitation causes the affected process to crash, resulting in a persistent denial of service (DoS) until the service or device is restarted. 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)

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.