Critical Auth Bypass Found in IBM Langflow OSS

IBM Langflow OSS versions 1.0.0 through 1.10.0 contain a critical vulnerability, tracked as CVE-2026-8505, that stems from a flaw in the platform's webhook authentication logic. With a CVSS score of 9.8, this vulnerability allows unauthenticated remote attackers to trigger the execution of any flow simply by knowing its UUID, effectively bypassing security controls.

What's at Risk

The vulnerability affects all deployments of IBM Langflow OSS within the 1.0.0 to 1.10.0 version range. Organizations that rely on Langflow for automated workflows or data processing are at significant risk, particularly if their instances are exposed to the public internet.

Because the flaw exists in the default configuration—where WEBHOOK_AUTH_ENABLE is set to False—many default installations are inherently vulnerable out of the box. Any entity utilizing this software in a production or development environment should consider their workflows compromised if the instance is reachable by unauthorized parties.

How the Flaw Works

This vulnerability is a classic example of an authentication bypass, where a system fails to properly verify the identity of a requester before granting access to sensitive functionality. In general, when an application fails to validate credentials or API keys during a request, it allows unauthorized actors to interface directly with backend processes that were intended to be protected.

When such a flaw exists, an attacker can leverage the application's own features to perform actions that should require administrative or authenticated privileges. In many cases, if the application is designed to execute scripts, interact with databases, or call system commands, an attacker can pivot from a simple unauthorized request to Remote Code Execution (RCE), granting them significant control over the underlying server or container environment.

How to Protect Your Systems

• Immediately update your IBM Langflow OSS instance to the latest secure version provided by the vendor.
• Set WEBHOOK_AUTH_ENABLE to True in your configuration files to enforce mandatory API key validation.
• Restrict network access to your Langflow instance using firewalls or VPNs to ensure only authorized users can reach the service.
• Implement strict monitoring and logging of all webhook requests to identify and alert on suspicious or unauthorized execution attempts.
• Audit existing flow UUIDs to ensure they are not exposed in public repositories or client-side code.

Given the critical severity of this flaw and the ease with which it can be exploited, organizations must prioritize remediation immediately. Leaving such a vulnerability unpatched provides a direct path for attackers to execute unauthorized commands, which could lead to a complete system compromise or data breach.