Arbitrary file writes via uncontained knowledge-base paths
Published Aug 5, 2026 · Updated Aug 5, 2026
Path traversal in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote authenticated users to write files outside intended storage. The create_knowledge_base handler builds a filesystem path directly from the supplied knowledge-base name and creates it without resolving the path or checking containment. Any authenticated account that can call the Knowledge Bases API can create directories and write files wherever the Langflow process has filesystem permission.
Summary
What happened
Path traversal in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote authenticated users to write files outside intended storage. The create_knowledge_base handler builds a filesystem path directly from the supplied knowledge-base name and creates it without resolving the path or checking containment. Any authenticated account that can call the Knowledge Bases API can create directories and write files wherever the Langflow process has filesystem permission.
The record
- CVE
- CVE-2026-7869
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2026CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.10.3
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.
Weakness, pattern, technique
Public exploit references
- Knowledge Bases creation-endpoint traversal payloadproof of concept · demonstrated
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