CVE-2026-82278

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-28. The CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated
8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.8Exploit: No code on recordExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists dataelement bisheng versions before 2.6.0 as affected. No release containing a fix is confirmed on record.

BISHENG before 2.6.0 contains a remote code execution vulnerability in the workflow run_once endpoint that allows authenticated users to execute arbitrary Python code. Attackers can submit crafted Code node definitions to the POST /api/v1/workflow/run_once endpoint, which executes them with exec() without sandboxing, gaining access to filesystem, credentials, and internal network resources.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
56
EG Risk 56/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)
Severity88% × 45%
The EG Score, 8.8 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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 at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (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

August 28, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Aug 28, 2026
No fix on record yet.
Web page

BISHENG Authenticated Arbitrary Python Code Execution via Workflow run_once | Advisories | VulnCheck

https://www.vulncheck.com/advisories/bisheng-authenticated-arbitrary-python-code-execution-via-workflow-run-once
Web page

bisheng/src/backend/bisheng/api/services/workflow.py at v2.4.0 · dataelement/bisheng · GitHub

https://github.com/dataelement/bisheng/blob/v2.4.0/src/backend/bisheng/api/services/workflow.py
Web page

GitHub - dataelement/bisheng: BISHENG is an open LLM devops platform for next generation Enterprise AI applications. Powerful and comprehensive features include: GenAI workflow, RAG, Agent, Unified model management, Evaluation, SFT, Dataset Management, Enterprise-level System Management, Observability and more. · GitHub

https://github.com/dataelement/bisheng
Web page

Authenticated RCE via run_once endpoint -- missing ownership check on workflow and no code sandboxing · Issue #2189 · dataelement/bisheng · GitHub

https://github.com/dataelement/bisheng/issues/2189

Vendor Advisories for CVE-2026-82278(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 20× in last 7d / 103× 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 168 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 68 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82278?
CVE-2026-82278 is a high-severity vulnerability; its CVE record was published on August 28, 2026. BISHENG before 2.6.0 contains a remote code execution vulnerability in the workflow runonce endpoint that allows authenticated users to execute arbitrary Python code. Attackers can submit crafted Code node definitions to the POST /api/v1/workflow/runonce endpoint, which executes them with exec()…
When was CVE-2026-82278 made public?
CVE-2026-82278 was made public on July 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-82278 actively exploited?
CVE-2026-82278 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82278?
CVE-2026-82278 has a CVSS base score of 8.8 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-82278?
No fix for CVE-2026-82278 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 CVE record's CNA (VulnCheck) lists dataelement bisheng versions before 2.6.0 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-82278 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-82278?

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

Book a Demo →Browse All CVEs