dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-62350

HIGH · 7.2 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TDengine versions prior to 3.4.1.15 allow authenticated users with 'create udf' privilege to upload malicious shared libraries and install them as User Defined Functions, enabling arbitrary C code execution on the server through database queries.

MitigationUpgrade TDengine to version 3.4.1.15 or later. Review and audit existing UDFs for suspicious code, and restrict the 'create udf' privilege to trusted administrative users only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed TDengine version
    Use the TDengine CLI (taos) or check version via 'taos --version' or 'select server_version()' query
    Affected if The installed version is prior to 3.4.1.15 (e.g., 3.4.0.x, 3.3.x, etc.)
  2. Identify users with 'create udf' privilege
    Query the TDengine user privileges system catalog or permission tables; look for grants of the 'create udf' or UDF creation permission
    Affected if Any non-administrative or untrusted user account holds the 'create udf' privilege
  3. List installed User Defined Functions
    Query the UDF registry via TDengine system tables (e.g., information_schema.USER_DEFINED_FUNCTIONS or equivalent) or use 'SHOW UDFS' command if available
    Affected if Any UDFs are installed on the system, especially those from untrusted sources
  4. Verify UDF shared library files
    Locate UDF library storage directory in TDengine configuration and inspect any .so or .dll files for unexpected or suspicious entries
    Affected if Unknown or suspiciously named shared library files exist in the UDF directory

You are affected if TDengine version is prior to 3.4.1.15 AND any user possesses the 'create udf' privilege, regardless of whether malicious UDFs are currently installed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TDengine to version 3.4.1.15 or later. Review and audit existing UDFs for suspicious code, and restrict the 'create udf' privilege to trusted administrative users only.

Recommended fix High confidence

TDengine version 3.4.1.15 or later

  1. 1. Identify the current TDengine version running in your environment using 'taos -v' or checking the installation directory.
  2. 2. Download TDengine version 3.4.1.15 or later from the official GitHub releases page (github.com/taosdata/TDengine).
  3. 3. Before upgrading, backup all databases and configurations to prevent data loss.
  4. 4. Stop the TDengine service using 'systemctl stop taosd' or 'sc stop taosd' depending on your OS.
  5. 5. Upgrade TDengine to version 3.4.1.15 following the official upgrade guide for your installation method (package manager, Docker, or source compilation).
  6. 6. Restart the TDengine service using 'systemctl start taosd' or 'sc start taosd'.
  7. 7. Verify the upgrade was successful by running 'taos -v' and confirming the version shows 3.4.1.15 or later.
  8. 8. Review user privileges to ensure only trusted administrators have 'create udf' privilege moving forward.
Caveat Review release notes for any configuration or API changes between your current version and 3.4.1.15; UDF functionality may have modified behavior

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,910
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62350 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-62350 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data