Security readout for executives and security teams
Plain-English summary
Langflow OSS voice mode may mix API client state between tenants. A logged-in attacker could cause another user’s requests to consume the wrong upstream credentials, creating unauthorized charges and unreliable accountability records. The supplied CVSS score is 9.6, making exposed multi-tenant deployments an urgent business risk.
Executive priority
Treat affected shared deployments as an immediate remediation priority. The main business risks are fraudulent API consumption, cross-tenant exposure, disputed charges, and corrupted audit trails. Preserve relevant logs, reconcile provider billing, and prioritize vendor remediation over compensating controls alone.
Technical view
IBM Langflow OSS 1.0.0 through 1.10.0 reportedly mishandles shared voice-mode state. An authenticated, network-based attacker can manipulate cached client state across tenant boundaries, causing requests to use another tenant’s upstream API credentials. Reported impacts include credential-associated data exposure, request misattribution, and billing fraud; availability impact is not claimed.
Likely exposure
Highest exposure exists where affected Langflow versions provide voice mode to multiple authenticated users or tenants and connect to billable upstream APIs. Single-user deployments or installations without voice mode may have lower practical exposure, but the supplied sources do not establish that they are unaffected.
Exploitation context
Exploitation requires authenticated access but is reported as low complexity, remote, and requiring no victim interaction. The CVE is not listed as KEV in the supplied bundle, and no supplied source confirms active exploitation or public exploit availability.
Researcher notes
The supplied metadata maps this issue to CWE-639 and reports scope change with high confidentiality and integrity impact. However, the affected-version data is internally inconsistent: the description says 1.0.0 through 1.10.0, while the structured version list contains only 1.0.0 and marks default status unaffected. Confirm exact applicability with IBM.
Mitigation direction
- Review IBM advisory 7278209 and apply its vendor-supported patch or upgrade guidance promptly.
- Restrict voice mode access until remediation is verified, especially in shared or multi-tenant deployments.
- Rotate potentially affected upstream API credentials according to provider procedures.
- Review upstream billing and usage records for unexpected tenant or account attribution.
- Contact IBM for clarification if deployed version status is ambiguous.
Validation and detection
- Inventory Langflow OSS versions and identify installations running versions 1.0.0 through 1.10.0.
- Determine whether voice mode is enabled and accessible by multiple authenticated users or tenants.
- Confirm the installed remediation matches IBM advisory 7278209.
- Inspect logs for mismatches between Langflow users, upstream credentials, requests, and billing records.
- Verify cached API clients and credentials remain isolated between tenants using authorized defensive testing.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-10140 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N3.15.8ibmVulnerability scoring details
Base CVSS 3.1 score
9.6CriticalVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.ibm.com/support/pages/node/7278209CVE reference, ibm · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.