Quick answers
- Is CVE-2026-81268 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81268 being exploited in the wild.
- How severe is CVE-2026-81268?
- High severity, with a CVSS score of 8.1, published 10 September 2026.
- Which products and versions are affected?
- IBM Langflow OSS 1.0.0 through 1.11.5.
- Is there a fix for CVE-2026-81268?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81268 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81268?
- Check whether you run IBM Langflow OSS or Langflow 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 insufficient session expiration issue (CWE-613) in Langflow OSS 1.0.0 through 1.11.5. The database API-key validator does not verify whether the owning user account is active before granting authentication; API keys issued to users remain valid after their accounts are deactivated by an administrator. Additionally, the MCP (Model Context Protocol) HTTP API credential resolvers do not apply the same AUTO_LOGIN API-key guard enforced on standard authenticated endpoints, allowing unauthenticated requests to MCP endpoints to be resolved to the superuser in default configurations. An authenticated attacker with a valid API key can exploit this to execute flows and retrieve sensitive information. The attack requires network access and valid credentials but no user interaction. IBM recommends upgrading to version 1.11.6 or later.
Affected products
- IBM Langflow OSS 1.0.0 through 1.11.5
Timeline
- 2026-09-08: disclosed
- 2026-09-10: advisory