Quick answers
- Is CVE-2026-57271 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57271 being exploited in the wild.
- How severe is CVE-2026-57271?
- High severity, with a CVSS score of 8.3, published 2 July 2026.
- Which products and versions are affected?
- Geovision GeoWebPlayer V1.1.1.0.
- Is there a fix for CVE-2026-57271?
- A patch was published on 2026-07-02: Version V1.1.3.0 confirmed as unaffected/patched Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-57271 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57271?
- Check whether you run Geovision GeoWebPlayer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An improper validation of array index (CWE-129) exists in the WebSocket server functionality of GeoVision GeoWebPlayer version 1.1.1.0. The vulnerability occurs when processing the 'pause' command (and other similar commands like connectInfo and setStream), where an 'index' field is extracted from a JSON-formatted WebSocket message and used to access internal arrays without proper bounds checking. By providing a specially crafted index value, an attacker can trigger an out-of-bounds read or write, potentially leading to the execution of arbitrary code via corrupted function pointers. Exploitation requires the victim to visit a malicious website that communicates with the local WebSocket server. The issue is addressed in version V1.1.3.0.
Affected products
- GeoVision Inc. GeoWebPlayer V1.1.1.0
Timeline
- 2026-07-01: disclosed: Talos published vulnerability report TALOS-2026-2373
- 2026-07-02: advisory: CVE-2026-57271 published by GeoVision
- 2026-07-02: patched: Version V1.1.3.0 confirmed as unaffected/patched