Quick answers
- Is CVE-2026-17627 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17627 being exploited in the wild.
- How severe is CVE-2026-17627?
- Medium severity, with a CVSS score of 4.9, published 4 September 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.10.2.
- Is there a fix for CVE-2026-17627?
- A patch was published on 2026-09-03: Fix available in version 1.10.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17627 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-17627?
- Check whether you run Apple macOS, IBM Langflow OSS, Langflow or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authorization bypass (CWE-639) in the voice-mode WebSocket endpoint. The endpoint authenticates the user and validates the presence of a personal OpenAI API key, but fails to perform authorization checks to verify the user has permission to access the specified flow (identified via URL path parameter). An authenticated attacker can supply any flow identifier to read the flow's description field and inject messages into the workflow's conversation history. The injected messages are subsequently visible to the flow owner via the message monitor API. Flow execution is unaffected as it applies a separate authorization check. The vulnerability affects versions 1.0.0 through 1.10.2 and is fixed in version 1.10.3.
Affected products
- IBM Langflow OSS 1.0.0 through 1.10.2
Timeline
- 2026-09-04: disclosed
- 2026-09-03: patched: Fix available in version 1.10.3