Quick answers
- Is CVE-2026-85025 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-85025 being exploited in the wild.
- How severe is CVE-2026-85025?
- Critical severity, with a CVSS score of 9.8, published 10 September 2026.
- Which products and versions are affected?
- IBM Langflow 1.0.0 through 1.11.5.
- Is there a fix for CVE-2026-85025?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-85025 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-85025?
- Check whether you run Langflow. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CVE-2026-85025 is a broken access control vulnerability (CWE-863) affecting Langflow 1.0.0 through 1.11.5. Publicly shared MCP project transports and public flows containing MCP Tools components fail to apply the code-execution guard and session namespace scoping controls that are enforced on other anonymous execution surfaces. An unauthenticated network attacker can reach affected endpoints without authentication or user interaction, send malicious requests to publicly shared MCP endpoints to execute arbitrary code at the application's privilege level, and access or modify chat session data across users. The root cause is improper enforcement of security restrictions when MCP components are used in public flows. Patches are expected from IBM through standard security updates.
Affected products
- IBM Langflow 1.0.0 through 1.11.5
Timeline
- 2026-09-10: disclosed