# CVE-2026-45533: DataEase: Path Traversal Vulnerability

> Attackers can delete arbitrary server directories via path traversal in the bulk delete API, impacting data integrity and availability.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H`)
- **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:** 17 Jul 2026
- **Also known as:** GHSA-mwr5-hw6p-cqmg

## What is CVE-2026-45533?

CVE-2026-45533 is a high-severity path traversal vulnerability in dataease, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

DataEase is an open source data visualization and analysis tool. Prior to 2.10.23, DataEase export-center deletion can accept path traversal sequences such as ../ in the bulk delete API endpoint and pass attacker-controlled identifiers to ExportCenterManage.delete, allowing recursive deletion of arbitrary server directories through export task cleanup. This issue is fixed in version 2.10.23.

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

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


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

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

## Is CVE-2026-45533 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-45533 is a high-severity path traversal vulnerability in dataease, published on 15 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-45533 exists.

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

## Sources

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

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