GPT-Pilot contains a command injection vulnerability in the Executor.run() method

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

6.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-31246: 0.70% estimated exploitation activity in the next 30 days; percentile 53.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.createsubprocessshell() 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.

Published by the source

11 May 2026, 18:31 UTC

Last modified by the source

13 Jul 2026, 16:43 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-m85w-whwh-qvfx

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-m85w-whwh-qvfx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31246

Advisory: GPT-Pilot contains a command injection vulnerability in the Executor.run() method
IDs: CVE-2026-31246, GHSA-m85w-whwh-qvfx
Record: https://patchnext.com/advisories/cve-2026-31246 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gpt-pilot: affected <= 0.0.10

## Suggested inspection (read-only)
- `python -m pip show gpt-pilot`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gpt-pilot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m85w-whwh-qvfx (OSV record GHSA-m85w-whwh-qvfx lists affected ranges: PyPI gpt-pilot >=0 <=0.0.10)
- Verified: https://github.com/advisories/GHSA-m85w-whwh-qvfx (GitHub-reviewed advisory GHSA-m85w-whwh-qvfx lists affected ranges: PyPI gpt-pilot >=0 <=0.0.10)

Commands are suggestions: review each one before running it.