Unauthenticated code execution via unguarded public MCP endpoints
Published Sep 10, 2026 · Updated Sep 10, 2026
Incorrect authorization in IBM Langflow OSS 1.0.0 through 1.11.5 allows remote attackers to execute code through public MCP endpoints. Publicly shared MCP project transports and public flows containing MCP Tools components omit the code-execution guard and session namespace scoping used by other anonymous execution paths. An unauthenticated network request to a publicly shared project is sufficient to run code as the service process and read or alter chat sessions.
Summary
What happened
Incorrect authorization in IBM Langflow OSS 1.0.0 through 1.11.5 allows remote attackers to execute code through public MCP endpoints. Publicly shared MCP project transports and public flows containing MCP Tools components omit the code-execution guard and session namespace scoping used by other anonymous execution paths. An unauthenticated network request to a publicly shared project is sufficient to run code as the service process and read or alter chat sessions.
The record
- CVE
- CVE-2026-85025
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 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.11.5
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