# CVE-2026-109442: piflow 2.0.0 through 2.0.1 Unauthenticated RCE via Chat Agent exec_shell


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-9925-27m4-6rvp

## What is CVE-2026-109442?

CVE-2026-109442 is a critical vulnerability in cas-bigdatalab piflow, published on 20 Oct 2026. 

### Official description

piflow 2.0.0 through 2.0.1 contains a remote code execution vulnerability in its DeepAgents chat agent, whose POST /chat and POST /chat/stream endpoints lack authentication. Attackers can instruct the agent to call the exec_shell tool, which runs arbitrary commands via subprocess.run without human approval or an allow-list, exposing environment secrets such as LLM API keys and database credentials.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-109442 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109442 is a critical vulnerability in cas-bigdatalab piflow, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-109442 exists.

Affected product: cas-bigdatalab piflow. 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-109442/ (Markdown: https://insights.sbomify.com/CVE-2026-109442/index.md)
```

## Sources

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

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