CVE-2026-52199

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreHIGH confidence

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

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

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

An issue in Generic OEM UZ801_v2.1 4G LTE Router V3.4.3 allows a remote attacker to execute arbitrary code via the sbin/adbd component

CVSS v3
9.1
EG Score
9.1(high)
EG Risk
72(Attend)
EG Risk 72/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
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
45%
KEV
Not listed

Published

July 17, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GitHub - lamaper/CVE-2026-52199 · GitHub

https://github.com/lamaper/CVE-2026-52199

Vendor Advisories for CVE-2026-52199(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 45× 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-29 06:42 UTCGHSA enrichment
  2. 2026-07-29 02:32 UTCGHSA enrichment
  3. 2026-07-28 22:25 UTCGHSA enrichment
  4. 2026-07-28 17:33 UTCEG score recompute
  5. 2026-07-28 17:33 UTCGHSA enrichment
  6. 2026-07-28 15:37 UTCEPSS rescore
  7. 2026-07-28 13:26 UTCGHSA enrichment
  8. 2026-07-28 09:16 UTCGHSA enrichment
  9. 2026-07-28 05:06 UTCGHSA enrichment
  10. 2026-07-28 00:58 UTCGHSA enrichment
  11. 2026-07-27 20:52 UTCGHSA enrichment
  12. 2026-07-27 16:44 UTCEG score recompute
  13. 2026-07-27 16:44 UTCGHSA enrichment
  14. 2026-07-27 12:09 UTCGHSA enrichment
  15. 2026-07-27 08:01 UTCGHSA enrichment
  16. 2026-07-27 03:53 UTCGHSA enrichment
  17. 2026-07-26 23:46 UTCGHSA enrichment
  18. 2026-07-26 19:38 UTCGHSA enrichment
  19. 2026-07-26 15:31 UTCEG score recompute
  20. 2026-07-26 15:31 UTCGHSA enrichment
  21. 2026-07-26 14:54 UTCEPSS rescore
  22. 2026-07-26 11:23 UTCEG score recompute
  23. 2026-07-26 11:23 UTCGHSA enrichment
  24. 2026-07-26 04:37 UTCEG score recompute
  25. 2026-07-26 04:36 UTCGHSA enrichment
Show 20 more
  1. 2026-07-25 14:18 UTCEPSS rescore
  2. 2026-07-24 14:18 UTCEPSS rescore
  3. 2026-07-23 14:18 UTCEPSS rescore
  4. 2026-07-23 03:19 UTCEG score recompute
  5. 2026-07-23 00:22 UTCEG score recompute
  6. 2026-07-23 00:22 UTCGHSA enrichment
  7. 2026-07-22 14:08 UTCEPSS rescore
  8. 2026-07-21 15:25 UTCEPSS rescore
  9. 2026-07-20 18:38 UTCEG score recompute▲ 9.10
  10. 2026-07-20 18:38 UTCGHSA enrichment
  11. 2026-07-20 18:37 UTCMITRE cvelistV5CVSS v3 → 9.1 · severity → CRITICAL
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 02:30 UTCEG score recompute
  16. 2026-07-19 02:30 UTCGHSA enrichment
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-17 22:01 UTCNVD update
  19. 2026-07-17 19:50 UTCEG score recompute
  20. 2026-07-17 19:49 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52199?
CVE-2026-52199 is a critical vulnerability published on July 17, 2026. An issue in Generic OEM UZ801_v2.1 4G LTE Router V3.4.3 allows a remote attacker to execute arbitrary code via the sbin/adbd component
When was CVE-2026-52199 disclosed?
CVE-2026-52199 was first published in the National Vulnerability Database on July 17, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52199 actively exploited?
CVE-2026-52199 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.8% of all scored CVEs.
What is the CVSS score of CVE-2026-52199?
CVE-2026-52199 has a CVSS v3.1 base score of 9.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-52199?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52199, 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-52199

Explore →

Is Your Infrastructure Affected by CVE-2026-52199?

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

Start Free Scan →Browse All CVEs