# CVE-2026-62355: TDengine: Standard User permission unexpect

> A Data Reader admin_user in TDengine Cloud could improperly create UDFs, bypassing read-only restrictions intended for standard users.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026

## What is CVE-2026-62355?

CVE-2026-62355 is a medium-severity vulnerability in taosdata TDengine, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TDengine is an open source, time-series database optimized for Internet of Things devices. Prior to 3.4.1.15, a Data Reader admin_user on a TDengine Cloud DB instance could run create udf even though standard users should have read-only permissions for non-database objects and show dnodes and create user were denied. This issue is fixed in version 3.4.1.15.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-62355?


## How do I fix CVE-2026-62355?

No fix has been published for CVE-2026-62355 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-62355 being exploited?

There is no known exploitation of CVE-2026-62355 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62355 and fix it if it is affected.

What it is: CVE-2026-62355 is a medium-severity vulnerability in taosdata TDengine, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-62355 in the wild and no public exploit code.

Affected product: taosdata TDengine. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62355/ (Markdown: https://insights.sbomify.com/CVE-2026-62355/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62355
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62355
- OSV: https://osv.dev/vulnerability/CVE-2026-62355

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62355/
Summaries are generated and may contain mistakes; the official description above is the record.