CVE Intelligence
Analysis AI-assisted

CVE-2026-10140: IBM Langflow OSS voice mode cross-tenant API client reuse (IDOR)

IBM reports a critical flaw in Langflow OSS 1.0.0 through 1.10.0 voice mode, where API clients are reused across tenant boundaries. An authenticated attacker can manipulate cache state so that other users' requests are processed with incorrect upstream API credentials, causing billing and accountability misattribution. The record lists no fixed version and no confirmed exploitation.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

IBM has published a Vendor Advisory covering Langflow OSS voice mode. The issue is improper shared-state handling that allows API clients to be reused across tenant boundaries. The weakness is classified as CWE-639, authorization bypass through a user-controlled key. See the IBM Support advisory.

Impact

  • An authenticated user may manipulate cache state so that requests from other users are processed with incorrect upstream API credentials.
  • The record describes cross-tenant billing and accountability misattribution as the resulting consequences.
  • The CVSS 3.1 base score of 9.6 (critical) was provided by the CNA, with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N. Confidentiality and integrity impact are rated high, and availability impact is rated none.

Affected products and versions

  • Product: Langflow Langflow (IBM Langflow OSS).
  • Range in the record: 1.0.0 through 1.10.0 inclusive.
  • The record lists no fixed version. This does not mean no fix exists, so consult the IBM advisory for current guidance.

Exploitation status

  • The CVE is not listed in the CISA KEV catalog in this record.
  • No confirmed exploitation in the wild appears in the sources consulted.
  • EPSS probability is 0.0035 with percentile 0.26758, dated 2026-10-13.

Remediation and mitigation

  • Review the IBM advisory and determine whether a fixed build is available for your deployment.
  • Until remediated, consider restricting or disabling voice mode on affected instances if this is operationally feasible.
  • Rotate upstream API credentials used by affected instances and review whether shared credentials may have been used on behalf of other tenants.
  • Prioritize multi-tenant deployments, where the cross-tenant consequence is most relevant.

Detection guidance

  • Review upstream API usage logs for requests attributed to unexpected tenants or users.
  • Reconcile billing records against tenant activity to identify misattributed usage.
  • Correlate voice-mode session activity with credential usage to spot mismatches at a high level.

Limitations of the available information

  • The record does not provide a fixed version, patch details, or root-cause technical specifics beyond the description.
  • The cache implementation, any prerequisites beyond authentication, and the full scope of exposed data are unknown.
  • Only one vendor reference and two NVD and CVE.org source pages were available.

Frequently asked questions

Which Langflow OSS versions are affected by CVE-2026-10140?

The record lists IBM Langflow OSS versions from 1.0.0 through 1.10.0 inclusive as affected.

Is CVE-2026-10140 known to be actively exploited?

The record shows the CVE is not listed in CISA KEV, and no confirmed exploitation in the wild appears in the sources consulted.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.