Langflow OSS: Inadequate Encryption Strength
CVE-2026-9201 is a high-severity inadequate encryption strength vulnerability in Langflow OSS from IBM, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected Langflow OSS versions: 1.0.0 through 1.10.3. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.38% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Langflow to 1.11.0 or a later version.
- Read the advisory on ibm.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| IBM | Langflow OSS | 1.0.0 through 1.10.3 | Not stated |
| Langflow | Langflow | 1.0.0 up to, but not including, 1.11.0 | 1.11.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (us.ibm.com).
Official description
IBM Langflow OSS 1.0.0 through 1.10.3 could allow an authenticated attacker to execute arbitrary code due to a cryptographic weakness in the custom component validation mechanism. When the optional hardening mode that restricts execution to trusted component templates is enabled, the application validates component code using a truncated SHA‑256 hash. Because the hash comparison relies on only a portion of the digest, an attacker can craft malicious component code that collides with a trusted template hash and bypasses validation. Successful exploitation allows the attacker to introduce and execute unauthorized Python code within the Langflow process, defeating the intended security control and potentially leading to full compromise of the affected instance.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Inadequate Encryption Strength
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
How developers prevent this class of flaw
- Use an encryption scheme that is currently considered to be strong by experts in the field.
More Inadequate Encryption Strength vulnerabilities (CWE-326)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Langflow OSS
- 8.1 High severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Inadequate Encryption Strength vulnerabilities
- 7.5 High severity
- 9.1 Critical severity
- 7.4 High severity
- 8.8 High severity
- 7.5 High severity
- 9.1 Critical severity
Spotted an error? Tell us.