Unauthenticated flow execution via disabled webhook authentication
Published Jul 17, 2026 · Updated Jul 17, 2026
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers to execute flows through webhook endpoints. The webhook handler treats WEBHOOK_AUTH_ENABLE=False, the default, as permission to skip API-key validation and run a requested flow as its owner. A remote attacker must know a flow UUID; when that flow contains executable components, owner-context execution runs server-side code or interrupts the service.
Summary
What happened
Authentication bypass in IBM Langflow OSS 1.0.0 through 1.10.0 allows remote attackers to execute flows through webhook endpoints. The webhook handler treats WEBHOOK_AUTH_ENABLE=False, the default, as permission to skip API-key validation and run a requested flow as its owner. A remote attacker must know a flow UUID; when that flow contains executable components, owner-context execution runs server-side code or interrupts the service.
The record
- CVE
- CVE-2026-8505
- Published
- Jul 17, 2026
- Updated
- Jul 17, 2026
- Vendor
- IBM
- Product
- Langflow OSS
- Classifications
- CWE-306, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 17, 2026CVE publishedPublication date reported by the CVE source.
- Jul 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.0.0 <=1.10.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo