CVE-2026-10140

CRITICALPre-NVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

Score 9.6 from GitHub Security Advisory (severity: CRITICAL) published 2026-06-30. A secondary CVSS source baseline 9.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
9.6EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.6Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

IBM 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.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
43
EG Risk 43/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
The EG Score, 9.6 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
26th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 30, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Oct 7, 2026
No fix on record yet.
generic

Security Bulletin: Cross-Tenant API Key Reuse and Billing Fraud in Langflow Voice Mode Subsystem

https://www.ibm.com/support/pages/node/7278209

Vendor Advisories for CVE-2026-10140(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 409 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 309 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 15:02 UTCEG score recompute
  2. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  3. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  4. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  5. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  6. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  7. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  8. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  9. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  10. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  11. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  13. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  14. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  15. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  17. 2026-09-23 11:18 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  18. 2026-09-23 07:19 UTCEG score recompute
  19. 2026-09-23 07:19 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  22. 2026-09-18 11:00 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  23. 2026-09-18 06:48 UTCEG score recompute
  24. 2026-09-18 06:48 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  25. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 28th percentile
Show 75 more
  1. 2026-09-14 08:47 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  2. 2026-09-14 04:45 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-09-14 00:47 UTCEG score recompute
  4. 2026-09-14 00:47 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  5. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  6. 2026-09-13 13:15 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  7. 2026-09-13 09:15 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  8. 2026-09-12 15:09 UTCEG score recompute
  9. 2026-09-12 15:09 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  10. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  11. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  12. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  13. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 28th percentile
  14. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-09-06 14:35 UTCEG score recompute
  17. 2026-09-06 14:35 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  19. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  23. 2026-08-31 02:25 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  24. 2026-08-30 22:23 UTCEG score recompute
  25. 2026-08-30 22:23 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  26. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  27. 2026-08-30 18:00 UTCEG score recompute
  28. 2026-08-30 18:00 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  29. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  30. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  31. 2026-08-28 02:50 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  32. 2026-08-27 22:40 UTCEG score recompute
  33. 2026-08-27 22:40 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  34. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  35. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  36. 2026-08-25 05:06 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  37. 2026-08-25 01:06 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  38. 2026-08-24 21:07 UTCEG score recompute
  39. 2026-08-24 21:07 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  40. 2026-08-24 11:39 UTCEG score recompute
  41. 2026-08-24 11:39 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  42. 2026-08-24 04:49 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  43. 2026-08-24 00:49 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  44. 2026-08-23 20:50 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  45. 2026-08-23 16:50 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  46. 2026-08-23 12:51 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  47. 2026-08-23 08:52 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  48. 2026-08-23 04:46 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  49. 2026-08-23 00:47 UTCEG score recompute
  50. 2026-08-23 00:47 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  51. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  52. 2026-08-22 20:28 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  53. 2026-08-22 12:37 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  54. 2026-08-22 08:20 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  55. 2026-08-22 01:18 UTCEG score recompute
  56. 2026-08-22 01:18 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  57. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  58. 2026-08-21 21:19 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  59. 2026-08-21 17:20 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  60. 2026-08-21 13:06 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  61. 2026-08-21 09:02 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  62. 2026-08-21 04:47 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  63. 2026-08-20 23:56 UTCEG score recompute
  64. 2026-08-20 23:56 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  65. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  66. 2026-08-20 19:57 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  67. 2026-08-20 15:55 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  68. 2026-08-20 09:26 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  69. 2026-08-20 05:28 UTCEG score recompute
  70. 2026-08-20 05:28 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  71. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 13th percentile
  72. 2026-08-19 16:34 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  73. 2026-08-19 12:34 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  74. 2026-08-19 07:58 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6
  75. 2026-08-19 03:56 UTCGHSA enrichmentGHSA-p5v5-v74q-w38h · GitHub severity CRITICAL · GitHub CVSS 9.6

Frequently asked(5)

What is CVE-2026-10140?
CVE-2026-10140 is a critical-severity vulnerability; its CVE record was published on June 30, 2026. IBM 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,…
When was the CVE record for CVE-2026-10140 published?
The CVE record for CVE-2026-10140 was published on June 30, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 11, 2026; the record at its source may have been updated since.
Is CVE-2026-10140 actively exploited?
CVE-2026-10140 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (26th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10140?
CVE-2026-10140 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10140?
No fix for CVE-2026-10140 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-10140 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-10140

Explore →

Is Your Infrastructure Affected by CVE-2026-10140?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.