CVE-2026-85025
9.8IBM · Langflow OSS
IBM Langflow OSS 1.0.0 through 1.11.5 contains an authorization flaw in MCP project endpoints, allowing unauthenticated attackers to achieve remote code execution and manipulate chat sessions.
Executive summary
A critical vulnerability in IBM Langflow OSS allows unauthenticated remote code execution and unauthorized data access due to insufficient security controls on public endpoints.
Vulnerability
This is an authorization flaw (CWE-863) where improper enforcement of security restrictions on MCP project endpoints permits an unauthenticated attacker to bypass session isolation and execute arbitrary code.
Business impact
The ability for an unauthenticated user to execute arbitrary code on the host system poses an extreme risk of total system compromise. This vulnerability could lead to the theft of sensitive chat data, unauthorized modification of project configurations, and complete loss of system integrity, justifying its critical CVSS score of 9.8.
Remediation
Immediate Action: Update IBM Langflow OSS to version 1.11.6 immediately as specified in the official vendor advisory.
Proactive Monitoring: Review web server and application access logs for suspicious requests targeting the MCP project endpoints or unusual execution patterns originating from unauthenticated sessions.
Compensating Controls: Implement strict network access control lists to restrict access to the Langflow management interface to trusted IP addresses, and deploy a Web Application Firewall (WAF) to filter malicious payloads targeting the vulnerable endpoints.
Exploitation status
Public Exploit Available: No (exploit_available: false)
Analyst recommendation
Given the critical nature of this vulnerability and the potential for remote code execution, organizations must prioritize upgrading to version 1.11.6 without delay. The absence of confirmed active exploitation does not mitigate the extreme risk associated with an unauthenticated RCE, and immediate patching is the only effective long-term defense.
More IBM CVEs all →
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief critical section