How severe is CVE-2024-55890?

No CVSS score has been assigned to CVE-2024-55890 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-55890?

CVE-2024-55890 affects the following packages: dtale (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2024-55890?

Update dtale to 3.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55890 is resolved across your whole dependency graph.

How do I detect CVE-2024-55890 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dtale, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-55890 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is CVE-2024-55890 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-55890 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-55890?

CVE-2024-55890 has an EPSS (Exploit Prediction Scoring System) score of 2.4%, placing it in the 83th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-55890?

CVE-2024-55890 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2024-55890?

A Nuclei detection template exists for CVE-2024-55890, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-55890 published, and has it been updated?

CVE-2024-55890 was published on December 13, 2024 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2024-55890 — dtale

Fix: man-group/dtale@1e26ed3

CVE-2024-55890 is a Cross-site Scripting (XSS) vulnerability in dtale. A fix is available for dtale — see the affected versions and patch details below.

D-Tale allows Remote Code Execution through the Custom Filter Input

Also known asGHSA-832w-fhmw-w4f4PYSEC-2026-1320

Published

Dec 13, 2024

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-55890.

EPSS Exploitation Probability

via FIRST.org ↗

2.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs83th percentile — riskier than 83% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍dtale

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Users hosting D-Tale publicly can be vulnerable to remote code execution allowing attackers to run malicious code on the server.

Patches

Users should upgrade to version 3.16.1 where the update-settings endpoint blocks the ability for users to update the enable_custom_filters flag. You can find out more information on how to turn that flag on here

Workarounds

The only workaround for versions earlier than 3.16.1 is to only host D-Tale to trusted users.

References

See "Custom Filter" documentation

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`dtale`	all versions	3.16.1`pip install --upgrade 'dtale==3.16.1'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dtale, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dtale to 3.16.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-55890 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

How to detect CVE-2024-55890

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-55890 -u https://target

Template: D-Tale <= 3.16.0 - Pre-Auth RCE via Pandas Query Injection
Severity: critical
Impact: Attackers can execute arbitrary code on the server, potentially leading to full system compromise.
Remediation: Upgrade to version 3.16.1 where the `update-settings` endpoint blocks `enable_custom_filters` updates.

Template by ProjectDiscovery nuclei-templates (0x_Akoko), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

### Impact Users hosting D-Tale publicly can be vulnerable to remote code execution allowing attackers to run malicious code on the server. ### Patches Users should upgrade to version 3.16.1 where the `update-settings` endpoint blocks the ability for users to update the `enable_custom_filters` flag. You can find out more information on how to turn that flag on [here](https://github.com/man-group/dtale#custom-filter) ### Workarounds The only workaround for versions earlier than 3.16.1 is to only host D-Tale to trusted users. ### References See "Custom Filter" [documentation](https://github.c

O3 Security · Impact-Aware SCA

Is CVE-2024-55890 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works