# CVE-2026-19897: mangroup dtale Login Endpoint auth.py login excessive authentication

> Attackers can bypass rate limiting on the login endpoint, facilitating brute-force attacks against user accounts in dtale.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-8r5p-64x9-63r7

## What is CVE-2026-19897?

CVE-2026-19897 is a medium-severity vulnerability in mangroup dtale, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability has been found in mangroup dtale up to 3.22.0. This issue affects the function Login of the file dtale/auth.py of the component Login Endpoint. Such manipulation leads to improper restriction of excessive authentication attempts. The attack can be executed remotely. This attack is characterized by high complexity. The exploitability is assessed as difficult. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-799 (Improper Control of Interaction Frequency), CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2026-19897?


## How do I fix CVE-2026-19897?

No fix has been published for CVE-2026-19897 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19897 being exploited?

There is no known exploitation of CVE-2026-19897 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19897 and fix it if it is affected.

What it is: CVE-2026-19897 is a medium-severity vulnerability in mangroup dtale, published on 15 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19897 in the wild and no public exploit code.

Affected product: mangroup dtale. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19897/ (Markdown: https://insights.sbomify.com/CVE-2026-19897/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19897
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19897
- OSV: https://osv.dev/vulnerability/CVE-2026-19897

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19897/
Summaries are generated and may contain mistakes; the official description above is the record.