Skip to main content
VulnerabilityPublished Updated

CVE-2026-3515: prefecthq/prefect · Argument Injection

Affects prefecthq/prefectSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.5 High.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
prefecthqprefecthq/prefectAffected
  • ≥ unspecified, ≤ latest
Fixed in–
PyPIprefectpkg:pypi/prefectOther threatsAffected
  • =3.6.18
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, avoid using the vulnerable version 3.6.18 of prefecthq/prefect or restrict access to the GitHubRepository block. Monitor vendor channels for updates and apply patches promptly once released.

Description

Prefect version 3.6.18 contains a command injection vulnerability in the GitHubRepository block of the prefect-github integration. The vulnerability arises because the reference field is directly concatenated into a git clone command without proper sanitization, allowing injection of arbitrary git command-line options. This can lead to Server-Side Request Forgery (SSRF), credential theft, or remote code execution. The issue affects the aget_directory() and get_directory() methods. GitLab and BitBucket integrations are not affected as they use safer command construction methods.

References

Community reviews

Loading reviews…