Quick answers
- Is CVE-2026-62351 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62351 being exploited in the wild.
- How severe is CVE-2026-62351?
- High severity, with a CVSS score of 7.5, published 15 July 2026.
- Which products and versions are affected?
- taosdata TDengine < 3.4.1.15.
- Is there a fix for CVE-2026-62351?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-62351 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-62351?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in the transDecompressMsg() function within source/libs/transport/src/transComm.c. When the RPC layer receives a packet with the compression flag set (comp=1), it fails to verify that the packet is large enough to contain the 8-byte STransCompMsg structure before reading the contLen field. This leads to an out-of-bounds read, followed by an uncontrolled memory allocation and an integer underflow when calculating decompression lengths for LZ4. An unauthenticated attacker can trigger this remotely to cause an immediate server crash. The issue is fixed in version 3.4.1.15.
Affected products
- taosdata TDengine < 3.4.1.15
Timeline
- 2026-06-26: advisory: GitHub Security Advisory published
- 2026-07-15: disclosed: NVD publication date