CVE-2026-42363

CRITICALNVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

Score 9.3 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-27. NVD baseline CVSS 9.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.3EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

Published

April 27, 2026

Last Modified

May 19, 2026

Advisory Details (2)

Auto-updated Sep 23, 2026
No fix on record yet.
generic

Cyber Security - GeoVision

https://www.geovision.com.tw/cyber_security.php
generic

Vulnerability Reports - Latest network security threats and zeroday discoveries || Cisco Talos Intelligence Group - Comprehensive Threat Intelligence

https://talosintelligence.com/vulnerability_reports/

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 272 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:48 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-05 17:43 UTCEPSS rescore
  6. 2026-10-04 23:22 UTCEPSS rescore
  7. 2026-10-03 14:25 UTCEPSS rescore
  8. 2026-10-01 19:50 UTCEPSS rescore
  9. 2026-09-30 15:03 UTCEPSS rescore
  10. 2026-09-27 13:48 UTCEPSS rescore
  11. 2026-09-26 15:58 UTCEPSS rescore
  12. 2026-09-23 17:53 UTCEPSS rescore
  13. 2026-09-20 20:15 UTCEPSS rescore
  14. 2026-09-18 19:28 UTCEPSS rescore
  15. 2026-09-17 19:31 UTCEPSS rescore
  16. 2026-09-16 14:08 UTCEPSS rescore
  17. 2026-09-16 05:15 UTCEPSS rescore
  18. 2026-09-13 16:47 UTCEPSS rescore
  19. 2026-09-12 15:01 UTCEPSS rescore
  20. 2026-09-11 14:53 UTCEPSS rescore
  21. 2026-09-11 09:37 UTCEPSS rescore
  22. 2026-09-10 09:34 UTCEPSS rescore
  23. 2026-09-08 22:00 UTCEPSS rescore
  24. 2026-09-07 16:01 UTCEPSS rescore
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 05:06 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-08-30 19:17 UTCEPSS rescore
  5. 2026-08-30 01:22 UTCEPSS rescore
  6. 2026-08-28 21:41 UTCEPSS rescore
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-23 00:19 UTCEPSS rescore
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-20 22:55 UTCEPSS rescore
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 14:43 UTCEG score recompute
  16. 2026-08-17 14:43 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 09:47 UTCGHSA enrichment
  20. 2026-08-16 05:41 UTCEG score recompute
  21. 2026-08-16 05:41 UTCGHSA enrichment
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 01:30 UTCEPSS rescore
  24. 2026-08-15 00:40 UTCGHSA enrichment
  25. 2026-08-14 20:33 UTCGHSA enrichment
  26. 2026-08-14 16:20 UTCGHSA enrichment
  27. 2026-08-14 12:14 UTCGHSA enrichment
  28. 2026-08-14 08:08 UTCGHSA enrichment
  29. 2026-08-14 04:02 UTCEG score recompute
  30. 2026-08-14 04:02 UTCGHSA enrichment
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 08:27 UTCGHSA enrichment
  33. 2026-08-13 01:56 UTCGHSA enrichment
  34. 2026-08-12 21:50 UTCGHSA enrichment
  35. 2026-08-12 17:44 UTCEG score recompute
  36. 2026-08-12 17:44 UTCGHSA enrichment
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 00:52 UTCGHSA enrichment
  39. 2026-08-11 20:46 UTCGHSA enrichment
  40. 2026-08-11 16:39 UTCEG score recompute
  41. 2026-08-11 16:39 UTCGHSA enrichment
  42. 2026-08-11 13:43 UTCEPSS rescore
  43. 2026-08-11 06:10 UTCGHSA enrichment
  44. 2026-08-11 02:05 UTCEG score recompute
  45. 2026-08-11 02:05 UTCGHSA enrichment
  46. 2026-08-11 00:00 UTCEPSS rescore
  47. 2026-08-10 13:12 UTCGHSA enrichment
  48. 2026-08-10 09:06 UTCGHSA enrichment
  49. 2026-08-10 05:01 UTCGHSA enrichment
  50. 2026-08-10 00:54 UTCGHSA enrichment
  51. 2026-08-09 20:49 UTCGHSA enrichment
  52. 2026-08-09 16:43 UTCEG score recompute
  53. 2026-08-09 16:43 UTCGHSA enrichment
  54. 2026-08-09 13:46 UTCEPSS rescore
  55. 2026-08-09 12:37 UTCGHSA enrichment
  56. 2026-08-09 07:20 UTCGHSA enrichment
  57. 2026-08-09 03:14 UTCEG score recompute
  58. 2026-08-09 03:14 UTCGHSA enrichment
  59. 2026-08-08 16:37 UTCEPSS rescore
  60. 2026-08-08 13:03 UTCGHSA enrichment
  61. 2026-08-08 08:56 UTCGHSA enrichment
  62. 2026-08-08 04:50 UTCGHSA enrichment
  63. 2026-08-08 00:44 UTCGHSA enrichment
  64. 2026-08-07 20:38 UTCGHSA enrichment
  65. 2026-08-07 16:32 UTCEG score recompute
  66. 2026-08-07 16:32 UTCGHSA enrichment
  67. 2026-08-07 12:26 UTCGHSA enrichment
  68. 2026-08-06 21:16 UTCGHSA enrichment
  69. 2026-08-06 17:10 UTCEG score recompute
  70. 2026-08-06 17:10 UTCGHSA enrichment
  71. 2026-08-06 13:46 UTCEPSS rescore
  72. 2026-08-06 11:21 UTCGHSA enrichment
  73. 2026-08-06 07:03 UTCGHSA enrichment
  74. 2026-08-06 02:57 UTCGHSA enrichment
  75. 2026-08-05 22:51 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-42363?
CVE-2026-42363 is a critical vulnerability published on April 27, 2026. 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…
When was CVE-2026-42363 disclosed?
CVE-2026-42363 was first published on April 27, 2026, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42363 actively exploited?
CVE-2026-42363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (21st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42363?
CVE-2026-42363 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-42363?
No fix for CVE-2026-42363 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-42363

Explore →

Is Your Infrastructure Affected by CVE-2026-42363?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.