Skip to main content
VulnerabilityPublished Updated

CVE-2026-7372: GeoVision GV-VMS V20.0.2 · Out-of-bounds Write

Affects GeoVision GV-VMS V20.0.2Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.0 Critical.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score
9.0Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 May 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 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GeoVision Inc.GV-VMS V20.0.2Affected
  • =20.0.2
Fixed in–

AI-suggested

Until an official fix is released, restrict network access to the WebCam Server Login interface to trusted users only and monitor for suspicious HTTP requests attempting to exploit this vulnerability. Avoid exposing the affected service directly to untrusted networks.

Description

A stack overflow vulnerability exists in the WebCam Server Login functionality of GeoVision GV-VMS V20 20.0.2. A specially crafted HTTP request can lead to an arbitrary code execution. An attacker can make an unauthenticated HTTP request to trigger this vulnerability. #### Stack-overflow via unconstrained sscanf The call to `sscanf` at [1] to split the `Buffer` variable into the `username` and `password` variables doesn't limit the size of the extracted content to match the destination buffers' sizes. In this case, if either the username or password decoded from the authorization string exceeds `40` characters (the size the stack variables `username` and `password`) then a stack overflow will occur. The data is controlled by an attacker, but sronger constraints (e.g.no null bytes) may make exploitation harder. A successful attack could lead to full code execution as SYSTEM on the machine running the service.

References

Community reviews

Loading reviews…