CVE-2026-52187

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_483ba0 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 7, 2026
No patch confirmed yet.
generic

CVEreport/518G/FUN_00483ba0/README.md at main · akuma-QAQ/CVEreport · GitHub

https://github.com/akuma-QAQ/CVEreport/blob/main/518G/FUN_00483ba0/README.md
generic

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

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52187?
CVE-2026-52187 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_483ba0 component
When was CVE-2026-52187 disclosed?
CVE-2026-52187 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-52187 actively exploited?
CVE-2026-52187 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-52187?
CVE-2026-52187 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-52187?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52187, 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-52187

Explore →

Is Your Infrastructure Affected by CVE-2026-52187?

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

Start Free Scan →Browse All CVEs