Unauthenticated cross-user file disclosure via OAuth fallback
Published Aug 5, 2026 · Updated Aug 5, 2026
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote attackers to read cross-user files through MCP. In verify_project_auth, OAuth projects skip the API-key requirement and fall through to a superuser lookup, while the streamable handler omits project ownership validation. The default-enabled MCP Composer and an OAuth-configured target project are required; no authentication or user interaction is needed.
Summary
What happened
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.3 allows remote attackers to read cross-user files through MCP. In verify_project_auth, OAuth projects skip the API-key requirement and fall through to a superuser lookup, while the streamable handler omits project ownership validation. The default-enabled MCP Composer and an OAuth-configured target project are required; no authentication or user interaction is needed.
The record
- CVE
- CVE-2026-8446
- Published
- Aug 5, 2026
- Updated
- Aug 5, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-862, CWE-200, CWE-639, CWE-306, CWE-288, T1190
- Attack vector
- network
- Privileges
- unauthenticated
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
- Upstream unauthenticated MCP resources/read reproductionproof 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