Quick answers
- Is CVE-2026-6596 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-6596 being exploited in the wild.
- How severe is CVE-2026-6596?
- High severity, with a CVSS score of 7.3, published 20 April 2026.
- Which products and versions are affected?
- langflow-base (PyPI) < 0.9.1, < 1.9.1, ECOSYSTEM:introduced=0,fixed=0.9.1.
- Is there a fix for CVE-2026-6596?
- Yes. langflow-base (PyPI): upgrade to 0.9.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-6596 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-6596?
- Check whether you run langflow-base (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- langflow-base (PyPI): upgrade to 0.9.1 or later
pip install "langflow-base>=0.9.1"
Technical details
A vulnerability exists in the `create_upload_file` function within `src/backend/base/Langflow/api/v1/endpoints.py` of Langflow. The endpoint lacks proper authentication and fails to enforce file size restrictions on uploaded content. A remote, unauthenticated attacker can exploit this by sending large volumes of data or excessively large files to the API, leading to resource exhaustion (disk space or memory) and a Denial of Service. While the vendor was reportedly unresponsive during initial disclosure, patches are available in version 0.9.1 for langflow-base.
Affected products
- langflow-ai langflow-base < 0.9.1
- langflow-ai langflow <= 1.1.0
Identifiers
- CVE-2026-6596
- GHSA-vvfc-fp59-m92g
- PYSEC-2026-2572
Timeline
- 2026-04-20: disclosed
- 2026-04-20: advisory