# CVE-2026-19896: mangroup dtale Flask Session Cookie app.py build_secret_key random values

> Attackers can predict Flask session cookies due to weak random key generation, potentially bypassing authentication 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:** 18 Aug 2026
- **Also known as:** GHSA-q2jc-92rc-h772

## What is CVE-2026-19896?

CVE-2026-19896 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 flaw has been found in mangroup dtale up to 3.22.0. This vulnerability affects the function build_secret_key of the file dtale/app.py of the component Flask Session Cookie. This manipulation causes insufficiently random values. Remote exploitation of the attack is possible. The attack's complexity is rated as high. It is stated that the exploitability is difficult. The exploit has been published and may be used. The pull request to fix this issue awaits acceptance.

Weakness: CWE-330 (Use of Insufficiently Random Values), CWE-310

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


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

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

## Is CVE-2026-19896 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19896 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19896 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19896 exists.

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-19896/ (Markdown: https://insights.sbomify.com/CVE-2026-19896/index.md)
```

## Sources

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

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