CVE-2026-42363
CRITICALDescription
An insufficient encryption vulnerability exists in the Device Authentication functionality of GeoVision GV-IP Device Utility 9.0.5. Listening to broadcast packets can lead to credentials leak. An attacker can listen to broadcast messages to trigger this vulnerability. When interacting with various Geovision devices on the network, the utility may send privileged commands; in order to do so, the username and password of the device need to be provided. In some instances the command is broadcasted over UDP and the username/password are encrypted using a cryptographic protocol that appears to be derivated from Blowfish. However the symmetric key used for the encryption is also included in the packet, and thus the security of the username/password only relies on the "obscurity" of the encryption scheme. An attacker on the same LAN can listen to the broadcast traffic once an admin user interacts with the device, and decrypt the credentials using their own implementation of the algorithm. With this password the attacker would have full control over the device configuration, allowing them to change its ip address or even reset it to factory default.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 8% of all known CVEs.
References
Related Vulnerabilities
Other CWE-656 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-10284 | Critical | 9.1 | 1.4% | - | - |
| CVE-2024-9138 | High | 7.2 | 1.1% | - | - |
| CVE-2024-12297 | Unscored | - | 0.8% | - | - |
| CVE-2020-10286 | High | 8.8 | 0.7% | - | - |
| CVE-2020-10277 | Medium | 6.4 | 0.4% | - | - |
| CVE-2024-5244 | Medium | 4.2 | 0.3% | - | - |
Common questions
How do I fix CVE-2026-42363?
No published fix for CVE-2026-42363 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-42363 being actively exploited?
Not that we know of. CVE-2026-42363 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.19% is the estimated probability that it will be exploited in the next 30 days. That is higher than 8% of all scored CVEs.
How severe is CVE-2026-42363?
CVE-2026-42363 has a CVSS v3 base score of 9.3, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-42363
Markdown
[](https://tridentstack.com/cve/CVE-2026-42363)HTML
<a href="https://tridentstack.com/cve/CVE-2026-42363"><img src="https://tridentstack.com/cve/badge/CVE-2026-42363.svg" alt="CVE-2026-42363"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-19.