What is the CVSS score of CVE-2026-9205?

CVE-2026-9205 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of IBM Langflow OSS are affected by CVE-2026-9205?

IBM Langflow OSS versions 1.0.0 through 1.10.3 contain a cryptographic weakness in key generation that exposes all stored API keys, credentials, and third-party connection secrets to decryption by…. A patch is available.

How to fix or mitigate CVE-2026-9205?

Within 24 hours, audit your infrastructure to identify all running instances of IBM Langflow OSS 1.0.0-1.10.3 and assess exposure scope. Within 7 days, apply the vendor-released patch to upgrade all affected Langflow deployments to the patched version and immediately rotate all API keys, credentials, and connection secrets that were previously encrypted and stored in the vulnerable system. Within 30 days, verify all external integrations authenticate correctly with the newly rotated credentials and conduct a post-patch security audit of database access logs to identify any unauthorized access during the vulnerability window.

IBM Langflow OSS CVE-2026-9205

EUVD-2026-53547 CRITICAL

Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) (CWE-338)

2026-08-05 ibm

GHSA-9pw3-x84f-xcwf

GHSA-jxw3-mjmx-3pqm

Information Disclosure IBM Langflow Oss

9.8

CVSS 3.1 · NVD

Severity by source

Vendor (ibm) PRIMARY

HIGH

qualitative

NVD

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.4 HIGH

Recovering the weak key and matching ciphertext raises complexity (AC:H); high confidentiality/integrity loss over stored secrets but no direct availability impact (A:N), so slightly below IBM's 9.8.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Aug 06, 2026 - 18:44 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Aug 06, 2026 - 18:37 vuln.today

cvss_changed

Severity Changed

Aug 06, 2026 - 18:37 NVD

HIGH CRITICAL

CVSS changed

Aug 06, 2026 - 18:37 NVD

7.4 (HIGH) 9.8 (CRITICAL)

Analysis Generated

Aug 05, 2026 - 18:46 vuln.today

CVE Published

Aug 05, 2026 - 18:09 cve.org

HIGH 7.4

DescriptionNVD

IBM Langflow OSS contains a weak cryptographic key derivation vulnerability in the ensure_fernet_key() function.

AnalysisAI

Predictable Fernet encryption key generation in IBM Langflow OSS (versions 1.0.0 through 1.10.3) stems from the ensure_fernet_key() function deriving keys from a cryptographically weak source (CWE-338), letting an attacker reconstruct the symmetric key that protects stored secrets such as API keys, credentials, and connection variables. Because the key is guessable rather than random, an actor who can read Langflow's encrypted data store can decrypt it and, depending on how the key is reused, potentially forge or tamper with protected values. There is no public exploit identified at time of analysis and EPSS is low (0.21%, 11th percentile), but IBM rates the flaw CVSS 9.8 and a vendor patch is available.

Technical ContextAI

Langflow is an open-source, Python-based low-code platform for visually building LLM and AI-agent workflows; it persists sensitive workflow secrets (model provider API keys, database and service credentials, global variables) in encrypted form. It uses Fernet, a symmetric authenticated-encryption scheme from the Python 'cryptography' library that requires a 32-byte key. The vulnerability lives in ensure_fernet_key(), the routine responsible for producing or normalizing that key: per CWE-338 (Use of a Cryptographically Weak Pseudo-Random Number Generator) the key material is derived from insufficient entropy or a predictable source rather than a CSPRNG, so the effective key space is small enough to reproduce or brute force. Because Fernet's confidentiality and integrity guarantees collapse entirely once the key is known, a weak key nullifies the protection over every secret encrypted with it. The affected component is identified by cpe:2.3:a:ibm:langflow_oss:*:*:*:*:*:*:*:*.

RemediationAI

Upgrade to a fixed release of IBM Langflow OSS above 1.10.3 as directed by the IBM advisory at https://www.ibm.com/support/pages/node/7282648 (patch confirmed available per vendor; an exact fixed version number is not stated in the provided data, so confirm the target release in that advisory before deploying). Because the underlying issue is a weakly derived encryption key, patching alone is insufficient if a weak key is already in use: after upgrading, rotate the Fernet/secret key and re-encrypt or re-enter all stored secrets, and rotate the underlying credentials (model provider API keys, database and service passwords) that were protected under the old key, since they must be treated as potentially recoverable. As compensating controls until you can patch, restrict network exposure of the Langflow instance (place it behind authentication/VPN and block direct internet access to its port), tightly limit filesystem and database access to the encrypted secret store, and avoid loading high-value long-lived credentials into affected instances; the trade-off is reduced accessibility for legitimate users and no protection for secrets already encrypted with a weak key.