Security readout for executives and security teams
Plain-English summary
TDengine versions before 3.4.1.15 allow a highly privileged database user to turn UDF creation into server-side code execution. This is serious because a database permission can become control of the TDengine server process, affecting confidentiality, integrity, and availability.
Executive priority
Treat as a high-priority patch and privilege review for TDengine environments. The privilege requirement lowers broad internet risk, but the server-side impact is severe if an administrator account or service credential is misused.
Technical view
The issue is CWE-94 in TDengine UDF handling. A user with create udf privilege could upload a crafted shared library, register it as a user-defined function, and trigger arbitrary C code execution through queries. CVSS 3.1 is 7.2: network reachable, low complexity, high privileges required, no user interaction.
Likely exposure
Organizations running TDengine before 3.4.1.15 are exposed if users, service accounts, or compromised credentials have create udf privilege. Risk is highest where TDengine is reachable from internal networks and database roles are broad or poorly audited.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. Exploitation requires high database privileges, but successful abuse can execute code on the TDengine server side with high impact.
Researcher notes
Evidence is limited to the CVE record and vendor advisory in the bundle. No public exploit status is cited here. Focus validation on version, UDF privilege assignments, UDF inventory, and whether TDengine is reachable by users or services beyond trusted administrators.
Mitigation direction
- Upgrade TDengine to version 3.4.1.15 or later.
- Review vendor advisory for any additional hardening guidance.
- Restrict create udf privilege to explicitly trusted administrators.
- Remove unnecessary UDF permissions from service accounts.
- Audit existing UDFs and shared libraries for unexpected entries.
Validation and detection
- Inventory all TDengine deployments and record exact versions.
- Confirm no instance remains below 3.4.1.15.
- List accounts or roles with create udf privilege.
- Review TDengine UDF registrations for unauthorized functions.
- Check database and host logs for suspicious UDF activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-62350 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9GitHub_MVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/taosdata/TDengine/security/advisories/GHSA-f7wh-p233-87xvCVE reference, GitHub_M · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.