Quick answers
- Is CVE-2026-45533 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45533 being exploited in the wild.
- How severe is CVE-2026-45533?
- Informational severity, with a CVSS score of 8.3, published 15 July 2026.
- Which products and versions are affected?
- DataEase < 2.10.23.
- Is there a fix for CVE-2026-45533?
- A patch was published on 2026-05-28: Fixed in version 2.10.23 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-45533 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45533?
- Check whether you run DataEase at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in the DataEase export-center bulk delete API endpoint. The application fails to properly sanitize user-provided identifiers before passing them to the ExportCenterManage.delete method. An authenticated attacker can inject path traversal sequences (e.g., '../../') to escape the intended directory and trigger a recursive deletion of arbitrary directories on the host server. This occurs during the export task cleanup process. The vulnerability is addressed in version 2.10.23 by implementing stricter validation on the identifiers used for file operations.
Affected products
- DataEase DataEase < 2.10.23
Timeline
- 2026-05-28: patched: Fixed in version 2.10.23
- 2026-05-28: advisory: GitHub Security Advisory published
- 2026-07-15: disclosed: CVE published to NVD