CVE-2026-3515: Prefect GitHub Integration Argument Injection Vulnerability

prefect Updated 18 Jul 2026

Summary

13/07/2026
No i
High
8.5

CVE-2026-3515: Prefect has an Argument Injection issue. Affects prefect versions < 3.6.18. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Prefect is an open-source workflow orchestration tool designed to help users build, schedule, and monitor data workflows. It integrates with various services, including GitHub, to facilitate version control and collaboration. The Prefect GitHub integration allows users to manage GitHub repositories directly within their workflows. However, a critical vulnerability has been identified in this integration, specifically in the GitHubRepository block, which can lead to severe security risks.

Vulnerability Detail

A vulnerability exists in the GitHubRepository block of the prefect-github integration in Prefect version 3.6.18. This issue allows an attacker to inject arbitrary git command-line options through the reference field. The reference field is concatenated directly into a git clone command string without proper sanitization, which is then parsed by shlex.split(). This flaw can lead to Server-Side Request Forgery (SSRF), credential theft, or remote code execution (RCE). The vulnerability affects both the aget_directory() and get_directory() methods in the src/integrations/prefect-github/prefect_github/repository.py file. The issue does not impact GitLab and BitBucket integrations, which utilize a safer command construction method.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, avoid using the reference field in the GitHubRepository block until you can update to a patched version. If you must use it, ensure that the input is sanitized and does not contain any potentially harmful command-line options.

Conclusion

The Prefect GitHub integration vulnerability (CVE-2026-3515) poses significant security risks due to improper handling of the reference field, allowing for command injection. Users are strongly advised to update to a patched version to mitigate these risks and ensure the security of their workflows.

See every vulnerability recorded for prefect →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 8.5, indicating a high severity level.

The vulnerability affects Prefect version 3.6.18 and earlier versions.

Exploitation of this vulnerability could lead to Server-Side Request Forgery (SSRF), credential theft, or remote code execution (RCE).

You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring signup.

As a workaround, avoid using the reference field in the GitHubRepository block until you can upgrade to a patched version.

Related vulnerabilities

Recent vulnerabilities recorded for prefect.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback