CVE-2026-42369 GeoVision GV-VMS V20 WebCam Server stack overflow vulnerability
Remote attackers can achieve SYSTEM code execution via stack overflow in the WebCam Server feature when remote access is enabled.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-42369?
CVE-2026-42369 is a critical memory corruption vulnerability in GeoVision Inc. GV-VMS V20.0.2, published on 4 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
GV-VMS V20 is a Video Monitoring Software used to gather the feeds of many surveillance cameras and manage other security devices. It is a native application accessed locally, but it is also possible to enable remote access via the "WebCam Server" feature. Once enabled, it is possible to access to the management and monitoring feature via a regular Web interface. This webersever is another native application, compiled without ASLR, which makes exploitation much easier and more likely.
Most of the features require authentication before being reachable and leverage a standard login page to grant access. However the `gvapi` endpoint uses its own authentication mechanism via an `HTTP Authorization` header. It supports both `Basic` authentication and the `Digest` modes of authentication.
#### Stack-overflow via unbound copy of base64 decoded string
The `b64decoder` string is sized dynamically, but it is then copied to the `Buffer` stack variable one character at the time at [0], and there's no bound-check. As such, if the decoded string is bigger than 256 characters (the size of the `Buffer` variable) then a stack overflow occurs. Because the data can be fully controlled by an attacker and lack of ASLR, this vulnerability can easily be exploited to gain full code execution as SYSTEM on the machine running the service.
Weakness: CWE-787
Which versions are affected by CVE-2026-42369?
How do I fix CVE-2026-42369?
No fix has been published for CVE-2026-42369 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2026-42369 being exploited?
There is no known exploitation of CVE-2026-42369 in the wild and no public exploit code.
Sources
Also known as GHSA-8wjc-q3qj-wc8j.