Langflow is affected by weaknesses in secret handling and sensitive configuration access

published 2026-08-05 3 mo ago modified 2026-10-24 15 d ago also GHSA-jxw3-mjmx-3pqm , PYSEC-2026-4235 , EUVD-2026-53547

cvss: 7.4; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits: 0; none known

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

Patch / fix

fixed in 2 links 3

pypi langflow 1.10.1
langflow langflow 1.11.0

github.com/langflow-ai/langflow@094694d commit
github.com/langflow-ai/langflow#13704 pull request
ibm.com/support/pages/node/7282648 advisory

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 3 mo ago (2026-08-06)

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.4	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
GitHub	3.1	9.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
pypi	langflow	<1.10.1	1.10.1

Affected products

IBM Langflow OSS

Classification

Weakness

CWE-338 Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
CWE-228 Improper Handling of Syntactically Invalid Structure

References

ibm.com /support/pages/node/7282648
vendor-advisory, patch, web
github.com /langflow-ai/langflow/pull/13704
web
github.com /langflow-ai/langflow/commit/094694d3f20c1da499f4d8dbac15c510609e3026
web
github.com /langflow-ai/langflow/security/advisories/GHSA-jxw3-mjmx-3pqm
web
nvd.nist.gov /vuln/detail/CVE-2026-9205
advisory
github.com /langflow-ai/langflow
package
pypi.org /project/langflow
package
github.com /advisories/GHSA-jxw3-mjmx-3pqm
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary