Authenticated service crash via escape-sequence buffer overrun
Published Jul 15, 2026 · Updated Jul 15, 2026
Stack-based buffer overflow in TAOS Data TDengine 3.4.1.6 and earlier allows remote authenticated users to crash the service via SQL. trimString() in source/libs/parser/src/parUtil.c checks room for one byte, then copies two-byte %, _, or \x escape sequences into the stack-based tmpTokenBuf buffer. An authenticated user must be able to submit crafted SQL string literals; a crash is demonstrated, while code execution is reported but not demonstrated.
Summary
What happened
Stack-based buffer overflow in TAOS Data TDengine 3.4.1.6 and earlier allows remote authenticated users to crash the service via SQL. trimString() in source/libs/parser/src/parUtil.c checks room for one byte, then copies two-byte %, _, or \x escape sequences into the stack-based tmpTokenBuf buffer. An authenticated user must be able to submit crafted SQL string literals; a crash is demonstrated, while code execution is reported but not demonstrated.
The record
- CVE
- CVE-2026-62349
- Published
- Jul 15, 2026
- Updated
- Jul 15, 2026
- Vendor
- TAOS Data
- Product
- TDengine
- Classifications
- CWE-121, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 15, 2026CVE publishedPublication date reported by the CVE source.
- Jul 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.4.1.14
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Direct trimString AddressSanitizer proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo