CVE-2026-62349
TDengine SQL parser stack OOB write enables DoS or potential RCE.
Is CVE-2026-62349 being exploited?
Not confirmed. CVE-2026-62349 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.57% probability of exploitation in the next 30 days.
How severe is CVE-2026-62349?
CVE-2026-62349 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62349?
Yes. A fix has been recorded for CVE-2026-62349. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62349 affect?
CVE-2026-62349 affects TDengine <= 3.4.1.6, Fixed in TDengine 3.4.1.14. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62349?
Upgrade to TDengine 3.4.1.14; restrict DB network exposure and monitor logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
One-byte stack out-of-bounds write when parsing SQL escape sequences, allowing service crash (DoS) and possible remote code execution via crafted queries.
Immediate action required
- affected< 3.4.1.14
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.