CVE-2026-88290: GeoVision GV-LPC2011/LPC2211 · Uncontrolled Resource Consumption
Affects GeoVision Inc. GV-LPC2011/LPC2211Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 10/25/2026, 16:58:58 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% 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:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wild: no evidence on record.
Not in CISA KEV and no source reports exploitation
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GeoVision Inc.GV-LPC2011/LPC2211 | Affected– | Fixed in– |
AI-suggested
Until a fix is available, consider limiting network exposure of the affected device and monitoring for unusual resource usage patterns related to VLSVR frame handling.
Description
GeoVision GV-LPC2211 V1.14 (260903) allows unauthenticated clients to declare unbounded VLSVR frame lengths and indefinitely delay blocking receives, allowing remote exhaustion of memory, connection, and worker resources.
Impact
The vulnerability allows remote unauthenticated attackers to exhaust critical server resources such as memory, network connections, and worker threads, leading to denial of service conditions. There is no impact on confidentiality or integrity reported. This can disrupt normal operation of the affected GeoVision GV-LPC2211 device.
Weaknesses
- CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.