CVE-2026-62349
Deferred Deferred - Pending Action

Heap-based Buffer Overflow in TDengine Time-Series Database

Vulnerability report for CVE-2026-62349, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-07-15

Last updated on: 2026-07-15

Assigner: GitHub, Inc.

Description

TDengine is an open source, time-series database optimized for Internet of Things devices. In 3.4.1.6 and earlier, source/libs/parser/src/parUtil.c trimString() checks space for only one byte before processing SQL string escape sequences \%, \_, or \x, allowing a one-byte out-of-bounds write to the stack buffer tmpTokenBuf that can cause denial of service and potentially remote code execution. This issue is fixed in version 3.4.1.14.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-15
Last Modified
2026-07-15
Generated
2026-08-05
AI Q&A
2026-07-16
EPSS Evaluated
2026-08-03
NVD
EUVD

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
taosdata tdengine 3.4.1.6
taosdata tdengine From 3.4.1.14 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.
CWE-121 A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a one-byte out-of-bounds write vulnerability in TDengine's trimString() function. It occurs when processing SQL escape sequences like \%, \_, or \x. The function checks space for only one byte but writes two, causing a stack buffer overflow. This can corrupt memory, leading to denial of service or remote code execution.

Detection Guidance

To detect this vulnerability, check the TDengine version installed on your system. Run: tdengine --version. If the version is 3.4.1.6 or earlier, the system is vulnerable. Additionally, monitor for crashes or unusual behavior when processing SQL queries containing escape sequences like \%, \_, or \x.

Impact Analysis

An authenticated user could exploit this by submitting crafted SQL queries with specific escape sequences. This may crash the application (DoS) or allow arbitrary code execution (RCE), potentially compromising the system.

Compliance Impact

This vulnerability could lead to unauthorized data access or system compromise, violating GDPR's integrity/confidentiality principles and HIPAA's security requirements for protected health information. Organizations using vulnerable TDengine versions may face compliance violations.

Mitigation Strategies

Upgrade TDengine to version 3.4.1.14 or later immediately. If upgrading is not possible, restrict access to SQL query submission to trusted users only and avoid using escape sequences in queries until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-62349. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart