What is the CVSS score of CVE-2026-8505?

CVE-2026-8505 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.6%.

Which versions of IBM Langflow OSS are affected by CVE-2026-8505?

IBM Langflow OSS versions 1.0.0 through 1.10.0 contain a critical flaw that allows attackers to gain unauthorized control of workflow processes without valid credentials, affecting any organization…. A patch is available.

How to fix or mitigate CVE-2026-8505?

Within 24 hours, inventory all IBM Langflow OSS instances in your environment, identify those running versions 1.0.0 through 1.10.0, and prioritize instances handling sensitive or production data. Within 7 days, apply the vendor-released patch from IBM's security advisory to all affected Langflow instances, verify successful remediation through version checks and functional testing, and confirm webhook authentication is enforced. Within 30 days, conduct a comprehensive security audit of all Langflow deployments, implement mandatory webhook authentication by setting WEBHOOK_AUTH_ENABLE=True on all instances, review webhook access logs for signs of unauthorized activity, and establish ongoing patch management procedures for this tool.

IBM Langflow OSS CVE-2026-8505

EUVD-2026-45272 CRITICAL

Missing Authentication for Critical Function (CWE-306)

2026-07-17 ibm

GHSA-9cc5-j3qq-69gv

IBM RCE Langflow Oss Authentication Bypass

9.8

CVSS 3.1 · Vendor: ibm

Severity by source

Vendor (ibm) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

9.8 CRITICAL

Network-reachable, no auth (PR:N) and no interaction against the default config; AC:L retained despite the UUID requirement, with full CIA impact via flow-driven RCE on the unchanged host scope.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (ibm).

CVSS VectorVendor: ibm

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 17, 2026 - 19:46 vuln.today

CVE Published

Jul 17, 2026 - 19:06 cve.org

CRITICAL 9.8

DescriptionCVE.org

IBM Langflow OSS 1.0.0 through 1.10.0 has a vulnerability in Langflow's webhook authentication logic allows unauthenticated users to trigger the execution of any flow. The system incorrectly bypasses API key validation when the WEBHOOK_AUTH_ENABLE configuration is set to False (which is the default setting). This allows a remote attacker who knows a flow's UUID to execute it as if they were the owner, potentially leading to Remote Code Execution (RCE).

AnalysisAI

Unauthenticated remote code execution in IBM Langflow OSS 1.0.0 through 1.10.0 stems from broken webhook authentication that skips API key validation whenever WEBHOOK_AUTH_ENABLE is False - which is the shipped default. Any remote attacker who learns a flow's UUID can invoke that flow's webhook endpoint as though they were its owner, running arbitrary flow logic and reaching RCE. No public exploit identified at time of analysis, but the CVSS 9.8 rating and default-vulnerable configuration make this a high-priority patch.

Technical ContextAI

Langflow is an open-source, Python-based visual builder for LLM and agentic workflows, where each 'flow' is a graph of executable components addressable by a UUID and triggerable via a webhook endpoint. The defect is an authentication logic error in the webhook handler: rather than treating a missing/disabled auth toggle as fail-closed, the code fails open - when the WEBHOOK_AUTH_ENABLE environment/config flag is False (the default), the API key check is bypassed entirely instead of being enforced. This is a classic authentication-bypass / missing-authentication-for-critical-function class of weakness (no CWE was assigned in the source data). Because flows in Langflow can execute arbitrary components - including code-executing, shell, or Python nodes - bypassing webhook auth escalates from unauthorized flow triggering to full RCE on the host. The affected package is identified by CPE cpe:2.3:a:ibm:langflow_oss:*:*:*:*:*:*:*:* across all 1.0.0-1.10.0 releases.

RemediationAI

Patch available per vendor advisory - upgrade IBM Langflow OSS to the fixed release identified in IBM's advisory at https://www.ibm.com/support/pages/node/7278921 (consult that page for the exact patched version, which was not enumerated in the source data, so do not assume a version number). As an immediate compensating control until you can upgrade, explicitly set WEBHOOK_AUTH_ENABLE=True so the API key check is enforced on webhook requests; be aware this requires all legitimate webhook callers to supply a valid API key and will break any integrations currently relying on unauthenticated triggering. Additionally, restrict network access to the Langflow webhook endpoints by placing the instance behind a reverse proxy or firewall that limits inbound traffic to trusted sources, and avoid exposing Langflow directly to the internet - the trade-off is reduced convenience for remote/webhook-driven automation. Treat flow UUIDs as sensitive and rotate any that may have leaked.