CVE-2026-109442: piflow 2.0.0 through 2.0.1
The National Vulnerability Database (NVD) record says piflow 2.0.0 through 2.0.1 lets unauthenticated callers of its chat endpoints make the DeepAgents chat agent run shell commands through exec_shell, with no human approval or allow-list.
The record
- Kind
- Vulnerability
- Source record
- CVE-2026-109442: piflow 2.0.0 through 2.0.1 contains a remote code execution vulnerability in its DeepAgents chat agent, whose (National Vulnerability Database record)
- Record published
- 2026-10-20
- Posted here
- 2026-10-20
- World
- Software agents · Enterprise work agents
- Controls concerned
- Actor identity verification C-A1; Destructive-action gate C-E3; Machine-enforceable scope C-M2
- Checked
- Checked against its record on 2026-10-22 by a reader who did not draft it; report
verification/reports/SIG-2026-10-20-001-2026-10-22.md.
A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.
Corrections
Changes to what this signal says, with the reason. Every earlier version is kept.
- 2026-10-22: Summary. Plain-language rule: abbreviation spelled out at first use; no claim changed (CVE record CVE-2026-109442). Found by the independent reader of 22 October 2026.
Show the change
Before: The NVD record says piflow 2.0.0 through 2.0.1 lets unauthenticated callers of its chat endpoints make the DeepAgents chat agent run shell commands through exec_shell, with no human approval or allow-list.After: The National Vulnerability Database (NVD) record says piflow 2.0.0 through 2.0.1 lets unauthenticated callers of its chat endpoints make the DeepAgents chat agent run shell commands through exec_shell, with no human approval or allow-list. - 2026-10-22: Title. Found in an independent read against the record on 22 October 2026: the record's affected range is 2.0.0 through 2.0.1 (VulnCheck advisory; CVE record).
Show the change
Before: CVE-2026-109442: piflow 2.0.0After: CVE-2026-109442: piflow 2.0.0 through 2.0.1
What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.
New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.
Get the weekly emailNewer: CVE-2026-77926: Aix-DB 1.2.4
Older: Wiz incident response report: an unnamed artificial intelligence (AI) agent system ran a multi-cloud intrusion