Authenticated host file access via unsafe Docker arguments
Published Aug 5, 2026 · Updated Aug 5, 2026
Incorrect privilege assignment in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote authenticated users to access host files. The shared MCP stdio source policy incompletely rejects Docker volume-mount and device-mapping arguments, allowing a submitted server configuration to attach host paths or devices to an MCP container. Low-privileged Langflow access and a Docker-based MCP server are required; successful exploitation permits host-file reading, modification, or exposure.
Summary
What happened
Incorrect privilege assignment in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote authenticated users to access host files. The shared MCP stdio source policy incompletely rejects Docker volume-mount and device-mapping arguments, allowing a submitted server configuration to attach host paths or devices to an MCP container. Low-privileged Langflow access and a Docker-based MCP server are required; successful exploitation permits host-file reading, modification, or exposure.
The record
- CVE
- CVE-2026-17626
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-266, T1611
- 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.
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