CVE-2026-62350

HIGHPre-NVD 7.27.2
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 57% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.2Exploit: Elevated riskExposed: 0

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

TDengine is an open source, time-series database optimized for Internet of Things devices. Prior to 3.4.1.15, a user with create udf privilege could upload a crafted shared library and install it as a user-defined function, such as eval, then execute arbitrary C code on the TDengine server side through database queries. This issue is fixed in version 3.4.1.15.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
48(Track*)
EG Risk 48/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
Severity72% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 18, 2026

Advisory Details (1)

Auto-updated Jul 15, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

UDF lead to RCE · Advisory · taosdata/TDengine · GitHub

https://github.com/taosdata/TDengine/security/advisories/GHSA-f7wh-p233-87xv

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-62350?
CVE-2026-62350 is a high vulnerability published on July 15, 2026. TDengine is an open source, time-series database optimized for Internet of Things devices. Prior to 3.4.1.15, a user with create udf privilege could upload a crafted shared library and install it as a user-defined function, such as eval, then execute arbitrary C code on the TDengine server side…
When was CVE-2026-62350 disclosed?
CVE-2026-62350 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62350 actively exploited?
CVE-2026-62350 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 56.9% of all scored CVEs.
What is the CVSS score of CVE-2026-62350?
CVE-2026-62350 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-62350?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62350, 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-62350

Explore →

Is Your Infrastructure Affected by CVE-2026-62350?

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