Authentication bypass in dtale

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2024-3408: 77.97% estimated exploitation activity in the next 30 days; percentile 99.57 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

man-group/dtale version 3.10.0 is vulnerable to an authentication bypass and remote code execution (RCE) due to improper input validation. The vulnerability arises from a hardcoded SECRETKEY in the flask configuration, allowing attackers to forge a session cookie if authentication is enabled. Additionally, the application fails to properly restrict custom filter queries, enabling attackers to execute arbitrary code on the server by bypassing the restriction on the /update-settings endpoint, even when enablecustomfilters is not enabled. This vulnerability allows attackers to bypass authentication mechanisms and execute remote code on the server.

Published by the source

6 Jun 2024, 21:30 UTC

Last modified by the source

10 Jun 2026, 19:00 UTC

Source last checked

26 Oct 2026, 13:26 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-v9q6-fm48-rx74

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-v9q6-fm48-rx74

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-3408

Advisory: Authentication bypass in dtale
IDs: CVE-2024-3408, GHSA-v9q6-fm48-rx74
Record: https://patchnext.com/advisories/cve-2024-3408 (revision 3, source checked 26 Oct 2026, 13:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dtale: affected <= 3.10.0

## Suggested inspection (read-only)
- `python -m pip show dtale`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dtale.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-v9q6-fm48-rx74 (OSV record GHSA-v9q6-fm48-rx74 lists affected ranges: PyPI dtale >=0 <=3.10.0)
- Verified: https://github.com/advisories/GHSA-v9q6-fm48-rx74 (GitHub-reviewed advisory GHSA-v9q6-fm48-rx74 lists affected ranges: PyPI dtale >=0 <=3.10.0)

Commands are suggestions: review each one before running it.