# CVE-2026-8505: Authentication Bypass in Webhook Endpoints Allowed Unauthorized Flow Execution

> Unauthenticated attackers can execute arbitrary flows in Langflow OSS due to default webhook authentication bypass, potentially leading to remote code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Jul 2026
- **Updated:** 23 Jul 2026
- **Also known as:** GHSA-cf6m-vc3m-7cgm, PYSEC-2026-4233

## What is CVE-2026-8505?

CVE-2026-8505 is a critical authentication bypass vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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).

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-8505?

3 open source packages ship an affected version, including langflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langflow` | PyPI | From 1.7.0 | 1.9.1 |
| `langflow` | PyPI | From 1.7.0 | 1.9.1 |
| `langflow` | PyPI | From 1.7.0 | 1.9.1 |

Products: Langflow Langflow.

## How do I fix CVE-2026-8505?

Upgrade langflow to 1.9.1 or later.

## Is CVE-2026-8505 being exploited?

There is no known exploitation of CVE-2026-8505 in the wild and no public exploit code.

## Other vulnerabilities in Langflow Langflow

- [CVE-2026-9198](https://insights.sbomify.com/CVE-2026-9198/): IBM Langflow Code Injection (critical 9.8, exploited in the wild)
- [CVE-2026-0770](https://insights.sbomify.com/CVE-2026-0770/): Langflow Inclusion of Functionality from Untrusted Control Sphere (critical 9.8, exploited in the wild)
- [CVE-2025-3248](https://insights.sbomify.com/CVE-2025-3248/): Langflow Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2025-34291](https://insights.sbomify.com/CVE-2025-34291/): Langflow Origin Validation Error (critical 9.4, exploited in the wild)
- [CVE-2026-33017](https://insights.sbomify.com/CVE-2026-33017/): Langflow Code Injection (critical 9.3, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8505 and fix it if it is affected.

What it is: CVE-2026-8505 is a critical authentication bypass vulnerability in Langflow Langflow, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-8505 in the wild and no public exploit code.

Affected packages and fixed versions:
- langflow (PyPI): affected from 1.7.0; fixed in 1.9.1
- langflow (PyPI): affected from 1.7.0; fixed in 1.9.1
- langflow (PyPI): affected from 1.7.0; fixed in 1.9.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8505/ (Markdown: https://insights.sbomify.com/CVE-2026-8505/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8505
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8505
- OSV: https://osv.dev/vulnerability/CVE-2026-8505

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8505/
Summaries are generated and may contain mistakes; the official description above is the record.