CVE-2026-110200 Langflow OSS is affected by multiple vulnerabilities
Medium 6.5
Published
Updated
Check this codebase for CVE-2026-110200 and fix it if it is affected.
What it is: CVE-2026-110200 is a medium-severity vulnerability in IBM Langflow OSS, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-110200 in the wild and no public exploit code.
Affected product: IBM Langflow OSS. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-110200/ (Markdown: https://insights.sbomify.com/CVE-2026-110200/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-110200?
CVE-2026-110200 is a medium-severity vulnerability in IBM Langflow OSS, published on 29 Oct 2026.
Official description
IBM Langflow OSS 1.0.0 through 1.12.4 could allow a remote authenticated attacker to obtain sensitive information due to cleartext storage of sensitive information.
Weakness: CWE-312
Which versions are affected by CVE-2026-110200?
How do I fix CVE-2026-110200?
No fix has been published for CVE-2026-110200 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-110200 being exploited?
There is no known exploitation of CVE-2026-110200 in the wild and no public exploit code.
Public exploit code: 1 proofs of concept on GitHub.
Sources
Also known as GHSA-cfm3-hm9j-hpqw.