dbcve.org
Gv Vms FirmwareOperating system · Geovision

CVE-2026-42370

CRITICAL · 9.8 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 21.0.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A stack overflow vulnerability in the WebCam Server Login functionality of GeoVision GV-VMS V20 20.0.2 allows unauthenticated attackers to send specially crafted HTTP requests that overflow a stack buffer, potentially leading to arbitrary code execution.

MitigationApply vendor patches when available; immediately restrict network access to the WebCam Server Login interface if exposure is not required, and implement input validation and bounds checking on all login parameters.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gv Vms FirmwareOperating system
Affected:< 21.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify GV-VMS firmware version
    Access the GV-VMS admin interface or check system information panel to determine the installed firmware version. Look for a version field typically displayed in the system about or status page.
    Affected if The installed version is below 21.0.0 (any version 20.x.x or earlier)
  2. Confirm WebCam Server Login is enabled
    Navigate to the WebCam Server settings in the GV-VMS administration panel and verify whether the Login functionality module is currently enabled or active.
    Affected if The WebCam Server Login feature is turned on and accessible
  3. Check network exposure of login interface
    Determine if the GV-VMS WebCam Server Login port (typically port 8081 or as configured) is exposed to untrusted networks by reviewing firewall rules, NAT configurations, or network boundary devices.
    Affected if The login interface is reachable from public or untrusted networks rather than only from internal trusted networks
  4. Review access logs for malformed requests
    Examine GV-VMS server logs for unusual or oversized HTTP POST requests to the login endpoint, particularly those containing abnormally long parameter strings.
    Affected if Logs show unexpected large login requests or signs of probing

You are affected if running GV-VMS firmware below version 21.0.0 with the WebCam Server Login feature enabled and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 21.0.0 or later
Fixed in 21.0.0
Interim mitigation

Apply vendor patches when available; immediately restrict network access to the WebCam Server Login interface if exposure is not required, and implement input validation and bounds checking on all login parameters.

Recommended fix High confidence

GeoVision GV-VMS Firmware 21.0.0

  1. Identify the current GeoVision GV-VMS firmware version by accessing the device administration interface or checking system information
  2. Navigate to the official GeoVision support or download page at www.geovision.com.tw
  3. Download the GV-VMS firmware version 21.0.0 or later
  4. Access the device's firmware upgrade interface, typically found under System Configuration > Maintenance > Firmware Upgrade
  5. Upload and apply the firmware version 21.0.0, following the on-screen instructions
  6. Verify the firmware upgrade was successful by checking the new version number
  7. Confirm that the WebCam Server Login functionality is operating normally after the upgrade
Caveat Review GeoVision release notes for version 21.0.0 to check for any configuration or feature changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gv Vms Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42370 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42370 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data