D TaleApplication · Man

CVE-2026-27194

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-21
Fix available
A fix is available. Upgrade to after 3.19.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

D-Tale versions before 3.20.0 contain an unauthenticated remote code execution vulnerability in the /save-column-filter endpoint. Attackers can send specially crafted requests containing malicious code that gets executed on the server, allowing complete compromise of the host system.

MitigationUpgrade D-Tale to version 3.20.0 or later. If immediate upgrade is not feasible, restrict public access to D-Tale instances and ensure proper authentication is enforced.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
D TaleApplication
Affected:<= 3.19.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify D-Tale installation
    Run 'pip list' or check your Python environment for the 'dtale' package. Alternatively, search for D-Tale processes or check where it may be running as a service.
    Affected if D-Tale package is present in your environment
  2. Determine installed D-Tale version
    Run 'pip show dtale' or check your package manager for the installed version number.
    Affected if Version is lower than 3.20.0 (versions 3.19.1 and below are affected)
  3. Check if /save-column-filter endpoint exists
    Inspect D-Tale source code for the route handler at /save-column-filter (typically in Flask/FastAPI routes). Verify the endpoint processes user input without proper sanitization.
    Affected if The endpoint exists and processes user-supplied data without sanitization
  4. Verify network exposure of D-Tale
    Check your firewall rules, reverse proxy configuration, or cloud security groups to determine if the D-Tale service port (typically port 4000) is accessible from public/untrusted networks.
    Affected if D-Tale is accessible from public networks without authentication restrictions

You are affected if D-Tale version 3.19.1 or lower is installed AND the /save-column-filter endpoint is accessible (with or without authentication).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.19.1
Vendor patch github.com →
Interim mitigation

Upgrade D-Tale to version 3.20.0 or later. If immediate upgrade is not feasible, restrict public access to D-Tale instances and ensure proper authentication is enforced.

Recommended fix High confidence

3.20.0

  1. 1. Stop the D-Tale service if it is currently running
  2. 2. Back up your current D-Tale installation and any associated data
  3. 3. Upgrade D-Tale to version 3.20.0 or later using pip: pip install dtale==3.20.0
  4. 4. Verify the upgrade was successful by checking the version: python -c "import dtale; print(dtale.__version__)"
  5. 5. Restart the D-Tale service
  6. 6. If hosting publicly, ensure proper authentication is configured and consider network segmentation to limit exposure

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in D Tale Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27194 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27194 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data