CVE-2026-5366 — Prefect GitRepository git argument injection leading to remote code execution
Prefect version 3.6.23 is vulnerable to remote code execution due to improper handling of user-controlled input in the `GitRepository` storage class. The `commit_sha` parameter, which is passed to git commands, lacks validation and does not include a `--` separator to distinguish user input from git flags. This allows attackers to inject arbitrary git flags, such as `--upload-pack`, enabling execution of external programs. Additionally, the `directories` parameter can be exploited to inject git flags during sparse-checkout operations. These vulnerabilities allow any user with deployment creation permissions to execute arbitrary commands on worker machines, compromising shared work pools in multi-tenant environments.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 1% (30-day exploitation probability)+9
- Technical severity (critical)+10
- CISA SSVC: exploitation "poc"+5
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Prefect Prefect, PrefectHQ Prefect).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.9 | CVSS 3.0 | Critical | 3.1 | 6.0 | security@huntr.dev via NIST National Vulnerability Database |
| 9.9 | CVSS 3.0 | Critical | — | — | @huntr_ai via CVE Program (cve.org) e CISA ADP |
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H (score shown at the top: security@huntr.dev) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 1.03%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Analysis and videos
CVE-2026-5366: Prefect GitRepository git argument injection leading to remote code execution
CVE-2026-5366 affects Prefect version 3.6.23 and is described as allowing remote code execution through unvalidated input in the GitRepository storage class. The record reports that user-controlled values reach git commands without a separator, allowing git flags to be injected. The CNA rates it critical with a CVSS 3.0 score of 9.9, and no confirmed exploitation appears in the sources consulted.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · prefecthq/prefecthq/prefect
- SSVC assessment updated
- Record published
- CVSS changed · 9.9
- Source status changed · → Analyzed
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-72538 PrefectHQ Prefect - Argument Injection Aug 11, 2026
- High CVE-2026-3514 Authentication Bypass in prefecthq/prefect Jun 2, 2026
- High CVE-2026-3515 Argument Injection in prefecthq/prefect May 24, 2026
- Medium CVE-2026-7725 PrefectHQ prefect GitRepository Pull storage.py argument injection May 4, 2026
- Medium CVE-2026-7724 PrefectHQ prefect Webhook/Notification validate_restricted_url toctou May 4, 2026
- High CVE-2026-7723 PrefectHQ prefect WebSocket Endpoint in missing authentication May 4, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-5366 is "Prefect GitRepository git argument injection leading to remote code execution", rated Critical. It affects Prefect (Prefect); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.9 describes technical severity. EPSS 1.03% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.