Critical IBM Langflow OSS 1.0.0 Vulnerability Tracked as CVE-2026-85025

What happened

CVE-2026-85025: IBM Langflow OSS 1. CVE-2026-85025 currently carries a CRITICAL 9 8 severity signal in the retained vulnerability data. The reported path can be reached without an authenticated session, increasing exposure wherever the vulnerable interface is network reachable.

Unauthenticated exposure changes the operational response because defenders cannot assume that an attacker would already need a compromised account before reaching the vulnerable function. IBM Langflow OSS 1 0 0 through 1 11 5 Langflow could allow an unauthenticated attacker to execute arbitrary code and access or modify chat sessions through publicly shared MCP project endpoints due to improper enforcement of public-flow security restrictions and session isolation controls.

The issue currently carries a CRITICAL 9 8 severity signal in the CyberDeltaForce record. The operational question is not simply the severity score, but whether the affected component is deployed, reachable, business-critical and protected by compensating controls. The current severity assessment is CRITICAL 9 8.

Real risk depends on exposure, exploitability, compensating controls and the importance of the affected asset—not the CVSS number alone. Inventory the affected product deployments and confirm whether the affected component and vulnerable release are present. Apply the vendor patch or mitigation for CVE-2026-85025 and validate the affected path after remediation.

The current source set does not report active exploitation of CVE-2026-85025; that status should be monitored rather than treated as proof that exploitation is impossible. The most useful validation after remediation is to confirm that the vulnerable path no longer permits the reported behavior and that the deployed release matches the vendor's corrected version.

So far, researchers have not reported exploitation, but that can change as vendor, government or threat-intelligence reporting develops.