Path Traversal in DataEase (CVE-2026-45532)
Summary
Path traversal in DataEase (CVE-2026-45532). Risk of unauthorized operations or information disclosure. Exploitable via FILE_SEPARATOR. Mitigation: upgrade to 2.10.23 or later.
Original description
The description as published by the source.
DataEase is an open source data visualization and analysis tool. Versions prior to 2.10.23 have a path traversal vulnerability. The root cause is that on Windows, the FILE_SEPARATOR is \, while the server only filters the / character during string truncation. The vulnerability has been fixed in v2.10.23. No known workarounds are available.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-45532 has been found in DataEase.
Attackers can target a specific entry point like FILE_SEPARATOR over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade DataEase to 2.10.23 or later.
If unsure, ask your IT team or search "DataEase CVE-2026-45532" on the vendor's site.
CVE-2026-45532 (DataEase) — CWE-22
Attack surface: FILE_SEPARATOR
Patched: 2.10.23 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in DataEase. Attackers reach the vulnerable code path via FILE_SEPARATOR.
Check the vendor advisory for the affected versions of DataEase. Attack surface: FILE_SEPARATOR.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.10.23.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'DataEase' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'DataEase' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
DataEaseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade DataEase to 2.10.23ステージング環境で 2.10.23 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- web github.com