Langflow: IBM Langflow OSS 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, and 1.0.0…
Langflow
More for Langflow RSS feed for Langflow
- Severity
- Critical, CVSS 9.1
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
- Record
- CVE-2026-8470
- Affects
- Langflow
- Known exploited
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Published
- Record first published by the source
- August 5, 2026
- Source last modified
- October 24, 2026
Description
IBM Langflow OSS 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, 1.0.0 through 1.10.3, and 1.0.0 through 1.10.3 use Python's non-cryptographic random module for generating Fernet encryption keys from user secrets under 32 characters. The deterministic Mersenne Twister PRNG produces identical keys for identical seeds, allowing attackers to reproduce encryption keys and decrypt stored API keys and authentication tokens.
Description quoted from the NVD record.
Who is affected
Langflow (also called IBM Langflow OSS) is a tool for building apps that use AI language models. This flaw affects versions 1.0.0 through 1.10.3. When the secret key someone sets for Langflow is shorter than 32 characters, the product turns it into an encryption key using a predictable method, so the same secret always produces the same key. An attacker could recreate that key and unlock the stored API keys (passwords that let Langflow use other services) and login tokens kept in the product. This flaw is rated Critical.
What to do
- Find out who runs Langflow for your organization: the person who installed it, or an IT provider or vendor who manages it for you.
- If someone in your organization runs it, ask them to check whether the installed version is 1.0.0 through 1.10.3, since those versions have this flaw.
- No fixed version is named for this flaw yet, so that person should check the vendor advisory linked on this page for a fixed release and install it as soon as one is available.
- If an IT provider or vendor runs Langflow for you, send them this advisory and ask when the update will be done.
Analysis written from the source record as of October 24, 2026 and reviewed before publishing.