Quick answers
- Is CVE-2026-57272 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-57272 being exploited in the wild.
- How severe is CVE-2026-57272?
- 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-57272?
- 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-57272 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-57272?
- 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
GeoVision GeoWebPlayer (version 1.1.1.0) contains multiple out-of-bounds (OOB) vulnerabilities within its WebSocket server, which handles commands like connectInfo, setStream, and audio. The root cause is improper validation of the 'index' field in incoming JSON messages, which is used to access internal arrays (such as array_of_IPCams and crit_sections) without bounds checking. An attacker can exploit this by hosting a malicious webpage that sends specially crafted WebSocket messages to the local server. This can result in OOB writes or the execution of arbitrary function pointers, potentially leading to remote code execution (RCE). The vulnerability is addressed in version V1.1.3.0.
Affected products
- GeoVision Inc. GeoWebPlayer V1.1.1.0
Timeline
- 2026-07-01: advisory: Talos vulnerability report published
- 2026-07-02: disclosed: CVE published to NVD
- 2026-07-02: patched: Version V1.1.3.0 confirmed as unaffected/patched