Authenticated cache disclosure and poisoning via access-control failure
Published Oct 6, 2026 · Updated Oct 6, 2026
Improper access control in IBM Langflow OSS 1.0.0 through 1.12.2 allows remote authenticated users to read sensitive data or poison vertex result caches. The vertex result caching subsystem fails to enforce access controls on cached results; IBM has not published the specific operation or missing check. Exploitation requires an authenticated account and can expose cached information or inject data into results consumed by the application.
Summary
What happened
Improper access control in IBM Langflow OSS 1.0.0 through 1.12.2 allows remote authenticated users to read sensitive data or poison vertex result caches. The vertex result caching subsystem fails to enforce access controls on cached results; IBM has not published the specific operation or missing check. Exploitation requires an authenticated account and can expose cached information or inject data into results consumed by the application.
The record
- CVE
- CVE-2026-97680
- Published
- Oct 6, 2026
- Updated
- Oct 6, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 6, 2026CVE publishedPublication date reported by the CVE source.
- Oct 6, 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.0.0 <=1.12.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started