dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-62355

MEDIUM · 5.4 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 →
60/100
Remediation priority · Elevated
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 Data Reader admin_user on a TDengine Cloud DB instance could run create udf even though standard users should have read-only permissions for non-database objects and show dnodes and create user were denied. 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 Cloud DB versions before 3.4.1.15 contained an authorization bypass where a Data Reader admin_user could execute the `create udf` (user-defined function) command despite having read-only permissions for non-database objects. This privilege escalation occurred because the permission check for UDF creation was not properly enforced, allowing a restricted admin user to create database objects.

MitigationUpgrade TDengine Cloud DB instances to version 3.4.1.15 or later to patch the authorization bypass in the UDF creation permission check.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify TDengine Cloud DB version
    Query the TDengine instance for its version using the appropriate client tool or API (e.g., taos -v, or SELECT %%b FROM %%information_schema.insufficient_versions or similar system query depending on your client). Compare the returned version number to 3.4.1.15.
    Affected if The installed version is TDengine Cloud DB and the version number is less than 3.4.1.15 (e.g., 3.4.1.14, 3.4.0.x, etc.).
  2. Verify user role assignment
    Check if the admin_user in question is assigned the Data Reader role, which should grant only read-only permissions to non-database objects. Query the user/role assignment tables in TDengine (such as SELECT * FROM %%information_schema.user_tasks or the appropriate system catalog depending on your TDengine deployment).
    Affected if The admin_user has the Data Reader role assigned, which should restrict them to read-only operations.
  3. Test UDF creation permission
    Attempt to execute the 'create udf' command using the restricted Data Reader admin_user account. This command should fail if permissions are properly enforced, but will succeed if the vulnerability exists.
    Affected if The Data Reader admin_user can successfully execute 'create udf' and create a user-defined function, indicating the authorization bypass is present.

You are affected if running TDengine Cloud DB version below 3.4.1.15 AND your environment has admin_user accounts with Data Reader role that can successfully execute 'create udf' commands.

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 Cloud DB instances to version 3.4.1.15 or later to patch the authorization bypass in the UDF creation permission check.

Recommended fix High confidence

TDengine 3.4.1.15

  1. 1. Backup your TDengine database, including all schemas, data, and user configurations
  2. 2. Stop the TDengine services on all nodes in your cluster
  3. 3. Update the TDengine package to version 3.4.1.15 using your package manager or download from the official repository (github.com/taosdata/TDengine/releases)
  4. 4. Verify the integrity of the downloaded package using checksums if available
  5. 5. Install the updated TDengine 3.4.1.15 packages on all cluster nodes
  6. 6. Review and update any configuration files that may have changed between your current version and 3.4.1.15
  7. 7. Start the TDengine services on all nodes
  8. 8. Verify the upgrade by logging in as the admin_user and confirming that create udf is properly restricted for Data Reader roles
Caveat No breaking changes mentioned in the CVE; standard upgrade precautions (backup, testing in staging) apply

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-62355 — 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-62355 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