dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-62348

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 a time-series database optimized for Internet of Things devices. Prior to 3.4.1.15, TDengine Enterprise allowed an authenticated low-privilege SQL user to run KILL SSMIGRATE <id> against an active shared-storage migration because mndProcessKillSsMigrateReq called mndKillSsMigrate while the intended MND_OPER_SSMIGRATE_DB privilege check was commented out. 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 Enterprise prior to 3.4.1.15 contains a privilege bypass vulnerability where an authenticated low-privilege SQL user can execute KILL SSMIGRATE <id> against an active shared-storage migration. The mndProcessKillSsMigrateReq function calls mndKillSsMigrate but the intended MND_OPER_SSMIGRATE_DB privilege check is commented out, allowing unauthorized termination of migration operations.

MitigationUpgrade TDengine Enterprise to version 3.4.1.15 or later where the privilege check is restored. Until then, limit SQL user permissions and monitor for unauthorized KILL SSMIGRATE commands in audit logs.

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
None
Integrity
Low
Availability
Low

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

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 installation and edition
    Run 'taos --version' or check the installed TDengine package to confirm Enterprise edition is in use. Community edition is not affected by this specific vulnerability.
    Affected if TDengine Enterprise edition is installed
  2. Check installed TDengine Enterprise version
    Run 'taos --version' or query the database with 'SELECT server_version()' to obtain the exact version number.
    Affected if Version is prior to 3.4.1.15 (for example, 3.4.1.14, 3.4.0.x, or earlier)
  3. Determine if shared-storage migration is configured
    Check for active or recent shared-storage migration operations. Query system tables or check migration configuration files if accessible. Look for SSMIGRATE-related processes or configurations.
    Affected if Shared-storage migration feature is in use or has been recently used
  4. Review SQL user privileges for KILL command access
    Query the grant information for SQL users using 'SHOW GRANTS' or inspect user permissions tables to see which users have permission to execute KILL commands.
    Affected if Low-privilege SQL users (without MND_OPER_SSMIGRATE_DB) can execute KILL SSMIGRATE commands
  5. Examine audit logs for KILL SSMIGRATE activity
    Search TDengine audit logs (typically in the log directory) for occurrences of 'KILL SSMIGRATE' commands, noting which users executed them and whether they should have had such privileges.
    Affected if KILL SSMIGRATE commands were executed by users lacking the MND_OPER_SSMIGRATE_DB privilege

The environment is affected if TDengine Enterprise version is prior to 3.4.1.15 AND shared-storage migration is in use AND low-privilege SQL users can execute KILL SSMIGRATE 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 Enterprise to version 3.4.1.15 or later where the privilege check is restored. Until then, limit SQL user permissions and monitor for unauthorized KILL SSMIGRATE commands in audit logs.

Recommended fix High confidence

3.4.1.15

  1. Upgrade TDengine Enterprise to version 3.4.1.15 or later

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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