# CVE-2026-6597: langflow-ai langflow Flow Using API core.py has_api_terms credentials storage

> Remote attackers can access unprotected stored API credentials in Langflow due to improper handling in the Flow Using API component.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-5jjf-wcvf-923w, PYSEC-2026-2565

## What is CVE-2026-6597?

CVE-2026-6597 is a medium-severity vulnerability in langflow-ai langflow, published on 20 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A weakness has been identified in langflow-ai langflow up to 1.8.3. Impacted is the function remove_api_keys/has_api_terms of the file src/backend/base/langflow/api/utils/core.py of the component Flow Using API. This manipulation causes unprotected storage of credentials. The attack can be initiated remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-256 (Plaintext Storage of a Password), CWE-255

## Which versions are affected by CVE-2026-6597?

3 open source packages ship an affected version, including langflow.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | All versions to 1.8.3 | None |
| `langflow` | PyPI | All versions to 1.8.3 | None |
| `langflow` | PyPI | All versions to 1.8.3 | None |

## How do I fix CVE-2026-6597?

No fix has been published for CVE-2026-6597 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6597 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6597 and fix it if it is affected.

What it is: CVE-2026-6597 is a medium-severity vulnerability in langflow-ai langflow, published on 20 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-6597 exists.

Affected packages and fixed versions:
- langflow (PyPI): affected all versions up to 1.8.3; no fix listed
- langflow (PyPI): affected all versions up to 1.8.3; no fix listed
- langflow (PyPI): affected all versions up to 1.8.3; no fix listed

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-6597/ (Markdown: https://insights.sbomify.com/CVE-2026-6597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6597
- OSV: https://osv.dev/vulnerability/CVE-2026-6597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6597/
Summaries are generated and may contain mistakes; the official description above is the record.