CVE-2026-57877

HIGHPre-NVD 8.68.6—
EchelonGraph scoreHIGH confidence

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-06-26. a secondary CVSS source baseline 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.6
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.6Exploit: NoneExposed: 0

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

An unauthenticated format string vulnerability exists in vlsvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper handling of externally controlled input during log message formatting in the login processing path. A remote attacker may exploit this vulnerability by sending crafted login data, potentially causing information disclosure, memory corruption, or a denial of service.

CVSS v3
8.6
EG Score
8.6(high)
EG Risk
43(Track)
EG Risk 43/100SSVC: Track

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
Severity86% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
16.1%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

Cyber Security - GeoVision

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

Vendor Advisories for CVE-2026-57877(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 84× 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.

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

Frequently asked(5)

What is CVE-2026-57877?
CVE-2026-57877 is a high vulnerability published on June 26, 2026. An unauthenticated format string vulnerability exists in vlsvr in GeoVision GV-LPC2011 and GV-LPC2211 V1.12 and earlier. The vulnerability is caused by improper handling of externally controlled input during log message formatting in the login processing path. A remote attacker may exploit this…
When was CVE-2026-57877 disclosed?
CVE-2026-57877 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57877 actively exploited?
CVE-2026-57877 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57877?
CVE-2026-57877 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-57877?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57877, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57877?

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

Start Free Scan →Browse All CVEs