CVE-2026-88286

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-10. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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

GeoVision GV-LPC2211 V1.13 improperly manages PTZ connection state, allowing an unauthenticated remote client to block the accept loop and prevent new PTZ connections.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 10, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Sep 10, 2026
No fix on record yet.
Web page

Cyber Security - GeoVision

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

Vendor Advisories for CVE-2026-88286(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 30× in last 7d / 114× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 125 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 25 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-88286?
CVE-2026-88286 is a high-severity vulnerability; its CVE record was published on September 10, 2026. GeoVision GV-LPC2211 V1.13 improperly manages PTZ connection state, allowing an unauthenticated remote client to block the accept loop and prevent new PTZ connections.
When was CVE-2026-88286 made public?
CVE-2026-88286 was made public on September 10, 2026: that is the date its CVE record's CNA, GeoVision Inc., gives for when the vulnerability was made public. The CVE record itself was published on September 10, 2026. EchelonGraph's copy of the record carries a last-modified date of September 10, 2026; the record at its source may have been updated since.
Is CVE-2026-88286 actively exploited?
CVE-2026-88286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-88286?
CVE-2026-88286 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-88286?
No fix for CVE-2026-88286 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. The vendor advisories EchelonGraph has for CVE-2026-88286 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-88286?

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

Book a Demo →Browse All CVEs