Langflow OSS is affected by multiple vulnerabilities
Langflow OSS versions 1.0.0 through 1.12.2 are affected. The fix is in 1.12.3, which IBM strongly recommends upgrading to now.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.12.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected product versions: Langflow OSS 1.0.0 through 1.12.2.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 16/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Langflow OSS, an IBM open-source AI workflow tool, has flaws that let a logged-in flow author write attacker-controlled content to any directory the service account can write to and read arbitrary files the service process can access, including configuration files, secrets, and database files. The attack can be carried out remotely over the network with low-privilege login and no user interaction.
Read the original description
IBM Langflow OSS 1.0.0 through 1.12.2 An authenticated flow author could write attacker-controlled file content into any directory writable by the service account, bypassing the platform's local file access isolation safeguard. Via a crafted on-disk index, the attacker could also read the contents of arbitrary files accessible to the service process — including configuration files, secrets, or database files stored under the application's data directory.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 23 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected product versions: Langflow OSS 1.0.0 through 1.12.2.Upgrade to a fixed version: 1.12.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- IBM Langflow OSS
From 1.0.0 · through 1.12.2
Evidence 1
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-97677
Is CVE-2026-97677 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The flaw lets an attacker write attacker-controlled file content into any directory writable by the service account, bypassing the local file access isolation safeguard. It can also read arbitrary files the service process can access, including configuration files, secrets, or database files.Source: ibm.com
Which versions are affected by CVE-2026-97677?
Langflow OSS: from 1.0.0 through 1.12.2.Source: cve.now feed data
Am I affected, and how do I check?
Langflow OSS versions 1.0.0 through 1.12.2 are affected. To check an installed copy, compare its version against that range.Source: ibm.com
How do I fix CVE-2026-97677?
Upgrade Langflow OSS to version 1.12.3, which IBM strongly recommends addressing now. The facts list no workaround.Source: ibm.com