# CVE-2026-72538: PrefectHQ Prefect - Argument Injection

> Authenticated attackers can achieve remote code execution on the Prefect server by injecting arguments into the git pull command via the branch field.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-42fh-94w4-956q

## What is CVE-2026-72538?

CVE-2026-72538 is a high-severity command injection vulnerability in PrefectHQ Prefect, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An argument injection vulnerability in PrefectHQ Prefect through 3.8.2 allows authenticated users to achieve remote code execution via the git_clone pull step branch field. The branch parameter is passed directly to git pull without sanitization, enabling injection of arbitrary git arguments. This represents a distinct code path from the incomplete fix applied for CVE-2026-5366 and allows command execution on the Prefect server.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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


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

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

## Is CVE-2026-72538 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72538 is a high-severity command injection vulnerability in PrefectHQ Prefect, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72538 in the wild and no public exploit code.

Affected product: PrefectHQ Prefect. 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-72538/ (Markdown: https://insights.sbomify.com/CVE-2026-72538/index.md)
```

## Sources

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

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