CVE-2026-52191

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-02. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

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

Buffer Overflow vulnerability in UTT nv518G nv518GV3v3.2.7-210919-161313 allows a remote attacker to cause a denial of service via the gohead/sub_444C8C component

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
37%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated Jul 6, 2026
No patch confirmed yet.
generic

CVEreport/518G/FUN_00444c8c at main · akuma-QAQ/CVEreport · GitHub

https://github.com/akuma-QAQ/CVEreport/tree/main/518G/FUN_00444c8c
generic

UTT��̩-רҵ·������������������ǽƷ��

https://utt.com.cn/downloadcenter.php?filetypeid=3&model=518G&lang=zhcn

Vendor Advisories for CVE-2026-52191(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 15× in last 7d / 65× 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-28 15:37 UTCEPSS rescore
  2. 2026-07-28 13:08 UTCGHSA enrichment
  3. 2026-07-28 01:06 UTCEG score recompute
  4. 2026-07-28 01:06 UTCGHSA enrichment
  5. 2026-07-27 13:06 UTCGHSA enrichment
  6. 2026-07-27 01:02 UTCEG score recompute
  7. 2026-07-27 01:01 UTCGHSA enrichment
  8. 2026-07-26 14:54 UTCEPSS rescore
  9. 2026-07-26 13:00 UTCEG score recompute
  10. 2026-07-26 13:00 UTCGHSA enrichment
  11. 2026-07-25 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 03:19 UTCEG score recompute
  15. 2026-07-22 14:08 UTCEPSS rescore
  16. 2026-07-21 15:25 UTCEPSS rescore
  17. 2026-07-20 17:08 UTCEPSS rescore
  18. 2026-07-19 14:31 UTCEPSS rescore
  19. 2026-07-19 14:31 UTCEPSS rescore
  20. 2026-07-19 02:29 UTCEPSS rescore
  21. 2026-07-18 10:04 UTCEPSS rescore
  22. 2026-07-17 02:20 UTCGHSA enrichment
  23. 2026-07-16 17:03 UTCEPSS rescore
  24. 2026-07-16 14:18 UTCGHSA enrichment
  25. 2026-07-16 02:19 UTCGHSA enrichment
Show 40 more
  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 14:18 UTCGHSA enrichment
  4. 2026-07-15 02:16 UTCGHSA enrichment
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-14 14:17 UTCGHSA enrichment
  8. 2026-07-14 02:18 UTCGHSA enrichment
  9. 2026-07-13 22:31 UTCEPSS rescore
  10. 2026-07-13 14:18 UTCGHSA enrichment
  11. 2026-07-13 06:13 UTCEPSS rescore
  12. 2026-07-13 06:13 UTCEPSS rescore
  13. 2026-07-13 02:19 UTCGHSA enrichment
  14. 2026-07-12 14:19 UTCGHSA enrichment
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-12 02:20 UTCGHSA enrichment
  17. 2026-07-11 14:20 UTCGHSA enrichment
  18. 2026-07-11 08:27 UTCEPSS rescore
  19. 2026-07-11 08:27 UTCEPSS rescore
  20. 2026-07-11 02:21 UTCGHSA enrichment
  21. 2026-07-10 14:20 UTCGHSA enrichment
  22. 2026-07-10 02:19 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 14:18 UTCGHSA enrichment
  26. 2026-07-09 02:17 UTCEG score recompute▲ 7.50
  27. 2026-07-09 02:17 UTCGHSA enrichment
  28. 2026-07-08 15:16 UTCEPSS rescore
  29. 2026-07-08 15:16 UTCEPSS rescore
  30. 2026-07-07 13:46 UTCEPSS rescore
  31. 2026-07-07 13:46 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 16:27 UTCEPSS rescore
  34. 2026-07-06 15:36 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  35. 2026-07-06 02:23 UTCEPSS rescore
  36. 2026-07-06 00:09 UTCGHSA enrichment
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-04 06:31 UTCEPSS rescore
  39. 2026-07-02 22:06 UTCEG score recompute
  40. 2026-07-02 22:06 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52191?
CVE-2026-52191 is a high vulnerability published on July 2, 2026. Buffer Overflow vulnerability in UTT nv518G nv518GV3v3.2.7-210919-161313 allows a remote attacker to cause a denial of service via the gohead/sub_444C8C component
When was CVE-2026-52191 disclosed?
CVE-2026-52191 was first published in the National Vulnerability Database on July 2, 2026, with the most recent update on July 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52191 actively exploited?
CVE-2026-52191 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.1% of all scored CVEs.
What is the CVSS score of CVE-2026-52191?
CVE-2026-52191 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-52191?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52191, 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-52191

Explore →

Is Your Infrastructure Affected by CVE-2026-52191?

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

Start Free Scan →Browse All CVEs