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

CVE-2026-62353

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.14, source/libs/parser/src/parTokenizer.c tGetToken() incremented past a trailing backslash in a SQL string literal such as 'abc\ and read one byte beyond the null terminator, allowing an authenticated user who can submit SQL queries to crash the server and possibly leak adjacent memory. This issue is fixed in version 3.4.1.14.

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

Buffer over-read vulnerability in TDengine's SQL parser tokenizer. The tGetToken() function in parTokenizer.c incorrectly increments past the null terminator when processing a string literal with a trailing backslash (e.g., 'abc\'), reading one byte beyond the buffer. An authenticated SQL user can trigger this to crash the server and potentially leak adjacent heap memory.

MitigationUpgrade TDengine to version 3.4.1.14 or later. As a compensating control, restrict SQL query execution privileges to trusted users until the upgrade can be completed.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 version
    Run 'taos --version' or check the installed package version using your system's package manager (dpkg, rpm, etc.)
    Affected if The installed version is earlier than 3.4.1.14
  2. Locate the TDengine server process
    Check if the TDengine server (taosd) is running using 'ps aux | grep taosd' or 'systemctl status taosd'
    Affected if The server process is running and responds to SQL queries
  3. Confirm SQL interface accessibility
    Verify that SQL query execution is available to users (check user privileges with 'SHOW GRANTS' or user role configuration)
    Affected if Untrusted or low-privilege authenticated users can execute SQL queries
  4. Verify parser is used
    The tokenizer in parTokenizer.c is automatically loaded when any SQL query is parsed, so simply sending any SQL query will invoke the vulnerable code path
    Affected if SQL queries can be sent to the server at all

A TDengine installation is affected if it is version 3.4.1.13 or earlier and accepts SQL queries from users who are not fully trusted.

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.14 or later. As a compensating control, restrict SQL query execution privileges to trusted users until the upgrade can be completed.

Recommended fix Moderate confidence

3.4.1.14

  1. 1. Identify the current TDengine installation version using 'taos --version' or checking the installed package.
  2. 2. If running a version prior to 3.4.1.14, plan for an upgrade to version 3.4.1.14 or later.
  3. 3. Before upgrading, review the TDengine 3.4.1.14 release notes for any migration requirements or compatibility notes.
  4. 4. Perform a full backup of the TDengine data directory (default: /var/lib/taos) and configuration files.
  5. 5. Stop the TDengine service using 'systemctl stop taosd' or 'service taosd stop'.
  6. 6. Upgrade TDengine to version 3.4.1.14 or latest stable version using the appropriate package manager or installation method (RPM/DEB/Docker).
  7. 7. Verify the upgrade was successful by running 'taos --version' and confirming the version is 3.4.1.14 or later.
  8. 8. Start the TDengine service using 'systemctl start taosd' or 'service taosd start'.
Caveat Review release notes for 3.4.1.14; minor version upgrades typically preserve backward compatibility but migration steps may be required

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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