Quick answers
- Is CVE-2026-19297 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19297 being exploited in the wild.
- How severe is CVE-2026-19297?
- Critical severity, with a CVSS score of 9.1, published 13 August 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.9.6.
- Is there a fix for CVE-2026-19297?
- A patch was published on 2026: Fixed in Langflow OSS 1.10.0 and newer Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19297 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-19297?
- Check whether you run Apple macOS, IBM Langflow OSS, Langflow or one of the others listed 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.
Technical details
The vulnerability is an improper restriction of excessive authentication attempts (CWE-307) in the login endpoint (POST /api/v1/login). Rate limiting is controlled via the LANGFLOW_RATE_LIMIT_ENABLED environment variable, which defaults to enabled with a 5 attempts per minute per IP limit using in-memory storage. However, when this control is explicitly disabled by an administrator or not validated post-deployment, an attacker with network access can perform unlimited brute force attacks at full speed against weak or default credentials. No authentication is required to reach the vulnerable endpoint. The fix is available in Langflow OSS 1.10.0 and newer.
Affected products
- IBM Langflow OSS 1.0.0 through 1.9.6
Timeline
- 2026-08-12: disclosed: IBM Security Bulletin published
- 2026: patched: Fixed in Langflow OSS 1.10.0 and newer