Vulnerability in dtale (CVE-2026-27194)
Summary
Vulnerability in dtale (CVE-2026-27194). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.20.0 or later.
Original description
The description as published by the source.
D-Tale is a visualizer for pandas data structures. Versions prior to 3.20.0 are vulnerable to Remote Code Execution through the /save-column-filter endpoint. Users hosting D-Tale publicly can be vulnerable to remote code execution allowing attackers to run malicious code on the server. This issue has been fixed in version 3.20.0.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
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-27194 has been found in dtale.
Risk of unauthorized operations or information disclosure.
What to do: upgrade dtale to 3.20.0 or later.
If unsure, ask your IT team or search "dtale CVE-2026-27194" on the vendor's site.
CVE-2026-27194 (dtale) — CWE-74
Patched: 3.20.0 — apply immediately
Workaround: There are no workarounds for versions < 3.20.0
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.
A vulnerability (CWE-74) exists in dtale.
Check the vendor advisory for the affected versions of dtale.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.20.0.
Workaround: There are no workarounds for versions < 3.20.0
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'dtale' . 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 'dtale' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dtaleを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no workarounds for versions < 3.20.0パッチが適用されるまでの応急処置として、There are no workarounds for versions < 3.20.0 を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade dtale to 3.20.0ステージング環境で 3.20.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com