# CVE-2026-31246: GPT-Pilot contains a command injection vulnerability in the Executor.run() method

> Attackers can execute arbitrary shell commands via unsanitized input in GPT-Pilot's executor, leading to remote code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-m85w-whwh-qvfx, PYSEC-2026-2501

## What is CVE-2026-31246?

CVE-2026-31246 is a medium-severity command injection vulnerability in n/a, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GPT-Pilot thru commit 0819827ce20346ef5f25b3fe29293cb448840565 (2025-09-03) contains a command injection vulnerability (CWE-78) in the Executor.run() method. During project execution, when the system prompts the user to confirm or modify a command to be run, it accepts free-text input without proper validation. The user-supplied input is directly passed to asyncio.create_subprocess_shell() for execution. This allows an attacker to replace the intended command with arbitrary shell commands, leading to remote code execution with the privileges of the GPT-Pilot process.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

3 open source packages ship an affected version, including gpt-pilot.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gpt-pilot` | PyPI | All versions to 0.0.10 | None |
| `gpt-pilot` | PyPI | All versions to 0.0.10 | None |
| `gpt-pilot` | PyPI | All versions to 0.0.10 | None |

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

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

## Is CVE-2026-31246 being exploited?

There is no known exploitation of CVE-2026-31246 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31246 is a medium-severity command injection vulnerability in n/a, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31246 in the wild and no public exploit code.

Affected packages and fixed versions:
- gpt-pilot (PyPI): affected all versions up to 0.0.10; no fix listed
- gpt-pilot (PyPI): affected all versions up to 0.0.10; no fix listed
- gpt-pilot (PyPI): affected all versions up to 0.0.10; no fix listed

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-31246/ (Markdown: https://insights.sbomify.com/CVE-2026-31246/index.md)
```

## Sources

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

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