dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-62351

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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, source/libs/transport/src/transComm.c transDecompressMsg() read STransCompMsg.contLen when pHead->comp == 1 without first validating that the RPC packet contained the 8-byte STransCompMsg structure, causing an unauthenticated out-of-bounds read, uncontrolled allocation, integer underflow, and server crash. 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's transDecompressMsg() function in transComm.c reads the compression length field (contLen) from STransCompMsg without validating that the incoming RPC packet actually contains the required 8-byte structure when compression is enabled (pHead->comp == 1). This allows unauthenticated attackers to trigger out-of-bounds memory reads, uncontrolled memory allocation, integer underflow, and cause the database server to crash.

MitigationUpgrade TDengine to version 3.4.1.15 or later which includes the missing bounds validation before reading the compression message structure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Identify TDengine installation and version
    Run 'taos --version' or check /etc/taos/taos.cfg for version info, or query the server via 'taos -s "select server_version()"'
    Affected if Installed version is earlier than 3.4.1.15
  2. Verify compression is enabled in RPC configuration
    Check the TDengine configuration file (commonly /etc/taos/taos.cfg or /var/lib/taos/cfg/taos.cfg) for 'rpcEnableCompression' or similar compression settings. Also check pHead->comp value in network traffic if possible.
    Affected if RPC compression is enabled (pHead->comp == 1) - the vulnerability only triggers when compression is enabled
  3. Confirm network exposure of TDengine RPC service
    Check which network interface the TDengine server binds to (typically port 6030/6031). Run 'netstat -tlnp | grep taosd' or 'ss -tlnp | grep taosd' to see listening ports and bound addresses.
    Affected if The TDengine RPC port (default 6030/6031) is bound to a non-localhost address, making it reachable from the network

A user is affected if running TDengine version earlier than 3.4.1.15 with RPC compression enabled and the service port exposed to network attackers.

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 which includes the missing bounds validation before reading the compression message structure.

Recommended fix High confidence

TDengine version 3.4.1.15

  1. 1. Verify current TDengine installation version using: taos --version or systemctl status taosd
  2. 2. Backup all data and configuration files before upgrading
  3. 3. Download TDengine version 3.4.1.15 or later from the official GitHub releases page (github.com/taosdata/TDengine)
  4. 4. Stop the TDengine service: sudo systemctl stop taosd or sudo taosd stop
  5. 5. Install the new version using the appropriate package manager or compilation method for your platform
  6. 6. Start the TDengine service: sudo systemctl start taosd or sudo taosd start
  7. 7. Verify the upgrade was successful by running: taos --version
  8. 8. Test that the database is operational and connections work correctly
Caveat Review TDengine 3.4.1.15 release notes for any migration requirements or breaking changes between your current version and 3.4.1.15

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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