Prefect has an Argument Injection issue

Exploitation

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

CVSS

8.5 · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-3515: 0.30% estimated exploitation activity in the next 30 days; percentile 22.54 (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.

A vulnerability in the GitHubRepository block of the prefect-github integration in Prefect version 3.6.18 allows an attacker to inject arbitrary git command-line options via the reference field. The reference field is concatenated directly into a git clone command string without proper sanitization, and then parsed by shlex.split(). This enables injection of options such as -c, leading to potential Server-Side Request Forgery (SSRF), credential theft, or remote code execution (RCE). The vulnerability affects both the agetdirectory() and getdirectory() methods in src/integrations/prefect-github/prefectgithub/repository.py. This issue does not affect the GitLab and BitBucket integrations, which use a safer list-based command construction approach.

Published by the source

26 May 2026, 13:30 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

26 Oct 2026, 13:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cw25-2p92-7f75

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-cw25-2p92-7f75

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

# Patch Next advisory brief: CVE-2026-3515

Advisory: Prefect has an Argument Injection issue
IDs: CVE-2026-3515, GHSA-cw25-2p92-7f75
Record: https://patchnext.com/advisories/cve-2026-3515 (revision 2, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.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 prefect: affected <= 3.6.18

## Suggested inspection (read-only)
- `python -m pip show prefect`: 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 prefect.
- 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-cw25-2p92-7f75 (OSV record GHSA-cw25-2p92-7f75 lists affected ranges: PyPI prefect >=0 <=3.6.18)
- Verified: https://github.com/advisories/GHSA-cw25-2p92-7f75 (GitHub-reviewed advisory GHSA-cw25-2p92-7f75 lists affected ranges: PyPI prefect >=0 <=3.6.18)

Commands are suggestions: review each one before running it.