Skip to main content
VulnerabilityPublished

CVE-2026-57878: GeoVision GV-LPCLPC2011/2211 · Stack-based Buffer Overflow

Affects GeoVision GV-LPCLPC2011/2211Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.8 Critical.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GeoVision Inc.GV-LPCLPC2011/2211Affected
  • =1.12
Fixed in–

AI-suggested

for this vulnerability as of the current information. Users should monitor the vendor's advisories for updates and apply any official fixes once available. Until a patch is released, consider limiting network exposure of affected devices and employing network-level protections such as firewalls to restrict access to the vulnerable service.

Description

An unauthenticated stack-based buffer overflow vulnerability exists in thttpd in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by insufficient bounds checking when processing web request parameters in a specific request path. A remote attacker may exploit this vulnerability by sending a crafted HTTP request with overly long input, resulting in memory corruption, denial of service, or potentially arbitrary code execution.

References

Community reviews

Loading reviews…