CVE-2026-62353 TDengine: Authenticated Out-of-Bounds Read in SQL Lexer tGetToken

Medium 5.4 Published Updated

An authenticated user can crash the TDengine server or leak memory by submitting a SQL query with a trailing backslash in a string literal.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-62353?

CVE-2026-62353 is a medium-severity memory corruption vulnerability in taosdata TDengine, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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.

Weakness: CWE-126, CWE-125

Which versions are affected by CVE-2026-62353?

How do I fix CVE-2026-62353?

No fix has been published for CVE-2026-62353 yet. Limit exposure of the affected software until one is available.

Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.

Is CVE-2026-62353 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62353 exists.

Sources

Is CVE-2026-62353 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free