# CVE-2026-19763: DTStack Taier Cluster Creation ClusterController.java FileUtils.deleteDirectory path traversal


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-v3r7-p73g-2j3x

## What is CVE-2026-19763?

CVE-2026-19763 is a medium-severity vulnerability in DTStack Taier, published on 14 Aug 2026. 

### Official description

A vulnerability was determined in DTStack Taier 1.4.0. Affected by this issue is the function FileUtils.deleteDirectory of the file ClusterController.java of the component Cluster Creation. This manipulation of the argument clusterName causes path traversal. Remote exploitation of the attack is possible. Upgrading to version 1.5.0 can resolve this issue. Patch name: ec8c59c76aceb04ab3080543ab2d9c6a4b674729. The affected component should be upgraded.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-19763 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19763 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19763 is a medium-severity vulnerability in DTStack Taier, published on 14 Aug 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19763 exists.

Affected product: DTStack Taier. 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-19763/ (Markdown: https://insights.sbomify.com/CVE-2026-19763/index.md)
```

## Sources

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

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