dbcve.org
CWE-129Weakness · CWE-129

CVE-2026-57266

HIGH · 8.3 CVSS v3.1 Published 2026-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges 8 weeks old

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
GeoWebPlayer (also called "Web Plugin" in the GV-VMS documentation and "WS Player" for VMS-Cloud) is an addon that can be installed with various GeoVision software (GV-VMS, GV-Cloud, ...). It creates a websocket server that expands the capabilities of the various web-interfaces provided by the GeoVision software and may be necessary for them to function properly. The Websocket server can accept various commands coming from localhost. Many of the commands will take an `index` value that is then used to access various arrays to enter critical sections, perform various actions via function calls, etc. However the `index` value is usually not checked for valid range, and as such it can be used to access multiple arrays out-of-bound. #### 2wayAudio command index-out-of-bound

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 · high confidence

GeoWebPlayer websocket server suffers from an out-of-bounds array access vulnerability in the 2wayAudio command. The 'index' parameter passed to commands is used directly to access internal arrays without validating its range, allowing an attacker to read or write beyond array boundaries by providing an out-of-range index value.

MitigationRestrict access to the GeoWebPlayer websocket server (currently accepting localhost connections) and implement proper bounds checking on all index parameters before array access. Network segmentation can limit exposure until a patch is available.

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

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
High
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/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. Confirm GeoWebPlayer installation
    Locate the GeoWebPlayer application on the system. Check for process names related to GeoWebPlayer or its websocket server component.
    Affected if GeoWebPlayer with a websocket server component is installed and running on the system.
  2. Identify websocket server accessibility
    Determine if the GeoWebPlayer websocket server is listening on any network interface. Check listening ports (commonly websocket ports 8080, 8443, or similar) and verify binding addresses. The summary indicates it accepts localhost connections by default.
    Affected if The websocket server is bound to a non-loopback interface or is otherwise accessible from outside localhost.
  3. Locate 2wayAudio command exposure
    Inspect the websocket server's available commands or API endpoints to confirm the 2wayAudio command is exposed. Check websocket message handlers or command registration code.
    Affected if The 2wayAudio command is registered and accessible through the websocket interface.
  4. Verify index parameter handling
    Examine the websocket server code or configuration for the 2wayAudio command handler. Determine if the index parameter from incoming requests is used directly to access internal arrays without bounds validation.
    Affected if The index parameter passed to the 2wayAudio command is used to access internal arrays without range checking, allowing out-of-bounds access.

A user is affected if GeoWebPlayer is running with its websocket server accessible (particularly from non-localhost sources) and the 2wayAudio command is exposed with the index parameter not being validated before array 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the GeoWebPlayer websocket server (currently accepting localhost connections) and implement proper bounds checking on all index parameters before array access. Network segmentation can limit exposure until a patch is available.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57266 — 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-57266 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