# CVE-2026-82278: BISHENG Authenticated Arbitrary Python Code Execution via Workflow run_once

> Authenticated attackers can execute arbitrary Python code via the workflow run_once endpoint, gaining access to filesystem and internal resources.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-h3mc-9q4p-46jg

## What is CVE-2026-82278?

CVE-2026-82278 is a high-severity code injection vulnerability in dataelement bisheng, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-82278?


## How do I fix CVE-2026-82278?

No fix has been published for CVE-2026-82278 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-82278 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82278 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-82278 and fix it if it is affected.

What it is: CVE-2026-82278 is a high-severity code injection vulnerability in dataelement bisheng, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82278 exists.

Affected product: dataelement bisheng. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-82278/ (Markdown: https://insights.sbomify.com/CVE-2026-82278/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-82278
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-82278
- OSV: https://osv.dev/vulnerability/CVE-2026-82278

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-82278/
Summaries are generated and may contain mistakes; the official description above is the record.