CVE-2026-10140
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIBM Langflow OSS 1.0.0 through 1.10.0 voice mode contains improper shared-state handling that allows reuse of API clients across tenant boundaries. An authenticated attacker can manipulate cache state to cause requests from other users to be processed using incorrect upstream API credentials, leading to cross-tenant billing and accountability misattribution.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIBM Langflow OSS 1.0.0-1.10.0 voice mode has improper shared-state handling in its caching layer. Authenticated attackers can manipulate cache state to cause API clients to be reused across tenant boundaries, resulting in requests from one tenant being processed with another tenant's upstream API credentials, causing cross-tenant billing and accountability issues.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 1.0.0, <= 1.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine installed Langflow versionRun 'pip show langflow' or check the package.json/version file in the Langflow installation directory to obtain the exact version numberAffected if The installed version falls within >= 1.0.0 and <= 1.10.0
-
Identify if voice mode is enabledInspect Langflow configuration files (config.yaml, settings.py, or environment variables) for voice mode settings such as VOICE_ENABLED, or check the frontend/admin UI for active voice integrationsAffected if Voice mode is enabled or has been used in the deployment
-
Examine the cache backend configurationReview the cache configuration in Langflow's config files, looking for Redis, Memcached, or in-memory cache settings; check if cache keys are prefixed with tenant identifiersAffected if Cache keys do not include tenant-specific prefixes or isolation markers
-
Verify API client instance isolationInspect the code or configuration governing API client reuse in the voice mode caching layer; check if API clients (credentials, sessions) are instantiated per-tenant or shared globallyAffected if A single API client instance is being reused across different tenants or tenant contexts are not separated in the client pool
-
Audit tenant context in cache lookupsReview cache get/set operations in the voice mode code path to confirm whether tenant ID or tenant context is required as part of the cache key lookupAffected if Cache lookups do not require tenant context to retrieve stored API client state
A user is affected if they are running Langflow version 1.0.0 through 1.10.0 with voice mode enabled and the cache layer lacks tenant-specific isolation in API client storage and retrieval.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict tenant isolation in the cache layer; ensure each tenant gets dedicated API client instances and cache keys are prefixed with tenant identifiers to prevent cross-tenant state leakage.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10140 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10140 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data