Authenticated credential exposure via incomplete API-key redaction
Published Apr 20, 2026 · Updated Apr 20, 2026
Credential exposure in Langflow OSS 1.8.0 through 1.8.3 allows remote authenticated users to read API keys through flow API responses. The remove_api_keys and has_api_terms logic incompletely identifies credential-bearing flow fields, leaving some values unredacted in API output. Exploitation requires high-privilege access and reveals only credentials present in affected flow data; no modification or service interruption is reported.
Summary
What happened
Credential exposure in Langflow OSS 1.8.0 through 1.8.3 allows remote authenticated users to read API keys through flow API responses. The remove_api_keys and has_api_terms logic incompletely identifies credential-bearing flow fields, leaving some values unredacted in API output. Exploitation requires high-privilege access and reveals only credentials present in affected flow data; no modification or service interruption is reported.
The record
- CVE
- CVE-2026-6597
- Published
- Apr 20, 2026
- Updated
- Apr 20, 2026
- Vendor
- OpenBMC Project
- Product
- Langflow OSS
- Classifications
- CWE-256, T1552
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 20, 2026CVE publishedPublication date reported by the CVE source.
- Apr 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.8.0
- Affected versionversion=1.8.1
- Affected versionversion=1.8.2
- Affected versionversion=1.8.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo