Skip to main content
CVE-2026-88287VulnerabilityPublished 09/10/2026

CVE-2026-88287: GeoVision GV-LPC2011/LPC2211 · Stack-based buffer overflow

Affects GeoVision Inc. GV-LPC2011/LPC2211Source CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 10/25/2026, 16:58:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GeoVision Inc.GV-LPC2011/LPC2211Affected
  • =1.13
Fixed in–

AI-suggested

Until a patch is available, consider restricting network access to the affected device's discovery service to trusted sources to reduce exposure.

Description

GeoVision GV-LPC2211 V1.13 fails to bound the number of Scopes tokens in unauthenticated ONVIF WS-Discovery Probe requests, allowing a remote attacker to corrupt stack control state and crash the discovery process.

Impact

An attacker can remotely send crafted ONVIF WS-Discovery Probe requests with excessive Scopes tokens to cause a stack-based buffer overflow, leading to stack corruption and crashing the discovery process on the affected device. This results in a denial of service condition. There is no indication of confidentiality or integrity impact.

Weaknesses

  • CWE-121Stack-based Buffer Overflow (opens in a new tab)

    Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14

    A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

References

Community reviews

Loading reviews…