Threat reportVulnerabilityTL-2026-2746
CVE-2026-42542: TDengine unauthenticated integer underflow lets a single RPC packet crash taosd
An integer underflow (CWE-191) in uvConnMayGetUserInfo() in TDengine 3.4.0.0 through 3.4.1.5 lets an unauthenticated remote attacker crash the taosd server with one crafted RPC packet over TCP/6030, causing denial of service. Fixed in 3.4.1.6. Ridge Security reports no in-the-wild exploitation telemetry and no known public exploit code; CVE-2026-42542 is not in CISA KEV as of the 2026.09.27 catalog. First disclosed .
Key facts
| Identifiers | TL-2026-2746, CVE-2026-42542 |
|---|---|
| Also known as | GHSA-vg95-j2hf-hvjx, TD-SEC-2026-001 |
| Severity | HIGH |
| CVSS | 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) |
| First disclosed | |
| Affected products | TDengine (TAOS Data) TDengine TSDB (taosd RPC service, TCP/6030) |
| Weaknesses (CWE) | CWE-191 |
| MITRE ATT&CK techniques | T0814 Denial of Service, T0819 Exploit Public-Facing Application, T1190 Exploit Public-Facing Application, T1499.004 Endpoint Denial of Service: Application or System Exploitation |
| Motivation | UNKNOWN |
| Target sectors | industrial, energy-utilities, automotive, iot, telecoms, building-automation, ev-charging, manufacturing |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 12 cited sources |
Detection coverage
As of 2026-09-28, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2746 across Splunk SPL, Microsoft KQL and Sigma, covering 8 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: taosd Segmentation Fault or Core Dump in Host Logs (CVE-2026-42542 Impact)
Detects taosd terminating on a segmentation fault or core dump in kernel, journald, or syslog data. The underflowed length reaches memcpy() and causes an out-of-bounds heap access, so the confirmed impact of CVE-2026-42542 is a taosd SIGSEGV. The kernel 'segfault at' line and systemd 'code=dumped, status=11/SEGV' line are the host-side proof of a successful crash, whether from exploitation or fuzzing.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1499.004, T0814, T0826
- Data sources: linux_syslog, journald, kernel_log
- Severity: high
- Confidence: high
Splunk SPL
``` CVE-2026-42542 - taosd crash (segfault / core dump) in host logs ```
(index=os OR index=linux) (sourcetype="syslog" OR sourcetype="linux_messages_syslog" OR sourcetype="journald") "taosd" ("segfault at" OR "SIGSEGV" OR "dumped core" OR "code=dumped" OR "status=11/SEGV")
| eval crash_signal=case(match(_raw,"(?i)segfault at"),"kernel_segfault", match(_raw,"(?i)dumped core|code=dumped"),"core_dump", true(),"sigsegv")
| stats count AS crash_events min(_time) AS first_crash max(_time) AS last_crash values(crash_signal) AS crash_types values(sourcetype) AS log_sources BY host
| eval crash_window_min=round((last_crash-first_crash)/60,1)
| convert ctime(first_crash) ctime(last_crash)
| table host crash_events crash_window_min crash_types log_sources first_crash last_crash
| sort - crash_eventsMicrosoft KQL
// CVE-2026-42542 - taosd segmentation fault or core dump
Syslog
| where TimeGenerated > ago(24h)
| where SyslogMessage has "taosd"
| where SyslogMessage matches regex @"(?i)segfault at|SIGSEGV|dumped core|code=dumped|status=11/SEGV"
| extend CrashType = case(
SyslogMessage contains "segfault at", "kernel_segfault",
SyslogMessage matches regex @"(?i)dumped core|code=dumped", "core_dump",
"sigsegv")
| summarize CrashEvents = count(), FirstCrash = min(TimeGenerated), LastCrash = max(TimeGenerated), CrashTypes = make_set(CrashType), LogSources = make_set(ProcessName) by Computer
| project Computer, CrashEvents, CrashTypes, LogSources, FirstCrash, LastCrash
| order by CrashEvents descSigma
title: TDengine taosd Segmentation Fault or Core Dump (CVE-2026-42542)
id: 2e8b6d14-5a7c-4f03-b1e9-6d4a90c2f835
status: experimental
description: 'Detects the taosd process crashing with a segmentation fault or core dump in Linux syslog or journald data. The CVE-2026-42542 integer underflow is passed to memcpy() as a copy length near 2^64, which faults and terminates taosd.'
references:
- https://github.com/taosdata/TDengine/security/advisories/GHSA-vg95-j2hf-hvjx
- https://ridgesecurity.ai/blog/one-packet-can-take-down-the-database-behind-industrial-operations-ridge-security-discovers-cve-2026-42542/
author: Threadlinqs Team
date: 2026-09-28
tags:
- attack.impact
- attack.t1499.004
- cve.2026-42542
logsource:
product: linux
service: syslog
detection:
keywords_process:
- 'taosd'
keywords_crash:
- 'segfault at'
- 'SIGSEGV'
- 'dumped core'
- 'code=dumped'
- 'status=11/SEGV'
condition: keywords_process and keywords_crash
falsepositives:
- Unrelated taosd defects, memory exhaustion, or hardware faults that also crash the process
- Deliberate fuzzing or crash testing in a lab
level: highKnown false positives:
- taosd crashes from unrelated bugs, out-of-memory conditions, or failing hardware
- Planned crash or fuzz testing on lab TDengine instances
Tuning notes: Adjust the index and sourcetype list to where kernel and systemd messages land. Correlate every hit with TCP/6030 network logs from the preceding two minutes to separate exploitation from unrelated faults. Exclude lab hosts by tag. Confirm version with taosd -V; 3.4.0.0 through 3.4.1.5 is vulnerable.
- Inbound TCP/6030 Connection Followed By taosd Crash Within 2 Minutes · unlock with TL Creds
- taosd Crash Loop or systemd Restart Storm (Sustained DoS) · unlock with TL Creds
- Loss of View - Steady taosd RPC Traffic Stops (Ingestion Gap) · unlock with TL Creds
- Brief Low-Volume TCP/6030 Sessions From Unexpected Sources (Crafted RPC Packet Shape) · unlock with TL Creds
- taosd Core Dump or Crash Report File Created · unlock with TL Creds
- Kernel-Audited Abnormal Termination (ANOM_ABEND) of taosd · unlock with TL Creds
- TDengine RPC Port 6030 Reached From Non-Allowlisted Source (CVE-2026-42542) · unlock with TL Creds
- Patched taosd Rejecting Malformed RPC Header (withUserInfo msgLen Too Short) · unlock with TL Creds
Indicators of compromise
As of 2026-09-28, Threadlinqs Intelligence tracks 8 indicators of compromise for TL-2026-2746.
Sample indicators (2 of 8)
- File hash:
6e95fe58a4e69509bd36aacbbc052ab264526942 - File hash:
003e8a5f102f6ee24ada79e087bdbbea1442ca88
Defanged, TLP:CLEAR. Full set of 8 indicators: unlock with TL Creds.
Technical analysis
CVE-2026-42542 is a pre-authentication integer underflow in the RPC transport layer of TDengine, an open-source distributed time-series database used for industrial telemetry, IoT, energy and utilities, connected-vehicle, EV-charging, telecom and building-automation data. The flaw is in uvConnMayGetUserInfo() at source/libs/transport/src/transSvr.c (line 860 per the vendor advisory) and affects TDengine 3.4.0.0 through 3.4.1.5. It was discovered by the Ridge Security Threat Research Team (Yan Zhou; the GitHub advisory credits discoverer Yan @ Ridge Security and reporter shook-zhou) while testing open-source applications used in IoT/OT environments.
Root cause: the function subtracts sizeof(STransMsgHead) plus a user-info offset from msgLen, a signed 32-bit integer (int32_t len) read directly from the attacker-controlled message header. Because sizeof(STransMsgHead) is an unsigned size_t, the signed value is promoted, and when msgLen is smaller than the header plus offset the subtraction wraps to a value near 2^64 on 64-bit systems (about 18 exabytes per the advisory). That value is passed to memcpy() as the copy length, producing an out-of-bounds heap access and a segmentation fault that terminates the taosd process. Ridge Security describes the fixed header as 64 or 192 bytes depending on message type; the advisory gives the required user-info offset as 24-128 bytes.
The vendor advisory documents the reproduction conditions: a malformed STransMsgHead with withUserInfo=1, version=3, and msgLen set to sizeof(STransMsgHead)+10 (too short for the required offset), carrying a valid CRC32 checksum. The CRC32 is a public, unkeyed integrity algorithm the sender computes, so it is not a barrier; no credentials, session state or user interaction are required, and the taosd RPC service listens on TCP/6030 by default. The vendor advisory and Ridge Security both state the confirmed impact is availability loss only; the advisory notes pre-crash heap memory corruption and that more sophisticated exploitation is conceivable, but no code-execution primitive has been demonstrated.
Exploitation status: Ridge Security states it has no telemetry indicating in-the-wild exploitation and is aware of no public exploit code. It holds a working proof of concept that reproduces the crash, withholds it from public release, and shares it with vetted defenders/vendors/CERTs under non-redistribution terms. The CVE is not listed in the CISA Known Exploited Vulnerabilities catalog (version 2026.09.27, 1,728 entries), and third-party trackers put its EPSS score below 1% (OpenCVE 0.00633; Strix/CyberStrike 0.54%). Independent coverage describes the fix as a three-line guard around the subtraction. Repeated transmission of the packet can sustain an outage when a supervisor such as systemd restarts taosd (a 'permanent crash cycle'); consequences include lost uncommitted writes, halted data collection, and lost visibility or alerting in OT environments. Ridge Security's researcher warned that outages could serve as cover for secondary attacks. Highest risk is on flat networks where TCP/6030 is broadly reachable and in embedded/OEM appliances where operators may not know TDengine is present; industrial environments also face patch delays from maintenance windows and vendor support requirements.
Remediation: upgrade to TDengine 3.4.1.6 or later, which rejects the packet when withUserInfo is set and msgLen is shorter than sizeof(STransMsgHead)+offset, logging 'withUserInfo set but msgLen %d too short (need %d)' before any arithmetic is done (fix commit 003e8a5f102f6ee24ada79e087bdbbea1442ca88; introducing commit 6e95fe58a4e69509bd36aacbbc052ab264526942 per OSV). Until patched, restrict TCP/6030 with host firewalls or network ACLs to authorized application hosts, inventory all instances including bundled ones, and monitor for taosd segmentation faults, crash loops and ingestion gaps. Ridge Security also noted, separately from this CVE, that TDengine defaults to MD5 password hashing and SHA-1 RPC connection signatures. The same Ridge Security post discloses an unrelated low-severity NanoMQ issue (CVE-2026-44639, CVSS 3.7, O(N^2) MQTT v5 property decoding, fixed in 0.24.14).
MITRE ATT&CK techniques by tactic:
Inhibit Response Function
Initial Access
T0819 Exploit Public-Facing Application; T1190 Exploit Public-Facing Application
Impact
T1499.004 Endpoint Denial of Service: Application or System Exploitation
Remediation
Patches
- TDengine 3.4.1.6 (validates msgLen against sizeof(STransMsgHead) + offset at the top of uvConnMayGetUserInfo()); fix commit 003e8a5f102f6ee24ada79e087bdbbea1442ca88
Immediate actions
- Upgrade TDengine (taosd) to 3.4.1.6 or later
- Restrict TCP/6030 with host firewall rules or network ACLs to authorized application hosts only
- Inventory every TDengine instance, including bundled/OEM/embedded deployments
Workarounds
- No vendor workaround beyond network-level restriction of TCP/6030 to trusted clients
Longer-term hardening
- Segment OT/IoT telemetry databases away from flat or broadly reachable networks; TCP/6030 should not be internet-exposed
- Alert on taosd segmentation faults, core dumps, and supervisor/systemd restart loops
- Alert on gaps in time-series data ingestion and on short-lived TCP/6030 connections from unexpected sources
- Inspect RPC traffic for packets whose declared msgLen is smaller than the fixed header size (never legitimate)
- Plan patch windows for OEM-bundled TDengine with the appliance vendor
Affected and fixed versions
- TDengine (TAOS Data) β TDengine TSDB (taosd RPC service, TCP/6030)
Vulnerable versions: 3.4.0.0 through 3.4.1.5
Fixed in: 3.4.1.6
Timeline
- TDengine publishes GitHub advisory GHSA-vg95-j2hf-hvjx (TD-SEC-2026-001) for CVE-2026-42542, rated High (CVSS 7.5), affecting 3.4.0.0-3.4.1.5 with the fix in 3.4.1.6; discoverer Yan of Ridge Security, reporter shook-zhou. The advisory documents the malformed-header reproduction conditions and the patch logic.
- CVE-2026-42542 is published in NVD (CWE-191, CVSS 7.5 from the GitHub CNA) and OSV, referencing the ver-3.4.1.6 release and the vendor advisory.
- NVD record last modified and marked Analyzed, with CPE cpe:2.3:a:tdengine:tdengine covering 3.4.0.0 through 3.4.1.5 (per OpenCVE/Strix); EPSS remains below 1%.
- OSV record modified; it lists introduced commit locked-ioc-1 (3.4.0.0) and fixed commit locked-ioc-2 (3.4.1.6).
- Ridge Security publishes its technical write-up: signed msgLen minus unsigned header size wraps to ~2^64 and reaches memcpy(); no in-the-wild telemetry, no public exploit; a working PoC is held privately and shared only with vetted defenders. Also discloses NanoMQ CVE-2026-44639.
- Trade press (Dark Reading, Security Boulevard, The IT Nerd) covers the flaw, stressing OT/IoT exposure, that TDengine may be embedded in appliances where operators are unaware of it, and that patching in industrial environments is slowed by maintenance windows.
- CISA KEV catalog version 2026.09.27 (1,728 entries) contains no CVE-2026-42542 or TDengine entry, consistent with the vendor's no-exploitation statement.
Sources cited
- Integer underflow in uvConnMayGetUserInfo() allows unauthenticated remote crash (DoS) - GHSA-vg95-j2hf-hvjx GitHub · Advisory · 2026-06-04
- NVD - CVE-2026-42542 NVD (NIST) · Advisory · 2026-06-10
- OSV - CVE-2026-42542 (GHSA-vg95-j2hf-hvjx) osv.dev · Advisory · 2026-06-10
- OpenCVE - CVE-2026-42542 (EPSS, CPE, KEV status) app.opencve.io · Advisory · 2026-07-23
- CISA Known Exploited Vulnerabilities catalog (checked: no CVE-2026-42542 entry, version 2026.09.27) CISA · Government advisory · 2026-09-27
- One Packet Can Take Down the Database Behind Industrial Operations: Ridge Security Discovers CVE-2026-42542 ridgesecurity.ai · Research · 2026-09-23
- TDengine TSDB Docs - Security Advisories (TD-SEC-2026-001) docs.tdengine.com · Vendor report · 2026-06-04
- TDengine release ver-3.4.1.6 GitHub · Code repository
- TDengine CVE-2026-42542: Unauthenticated Integer Underflow Crashes taosd with a Single Packet (DEV Community) dev.to · Blog
- One Packet Can Crash OT Servers in Industrial Sectors (Dark Reading) Dark Reading · News
- Security Boulevard: One Packet Can Take Down the Database Behind Industrial Operations securityboulevard.com · News · 2026-09-23
- New OT zero-day can take down a database with one packet, and you may not know it's there (The IT Nerd) itnerd.blog · News · 2026-09-24
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 12 sources; published ; last updated —.