Prefect develops a workflow orchestration and data-pipeline platform whose vulnerability profile centers on web-application authorization and session-management issues, specifically cross-site request forgery and incorrect authorization controls. The niche exposure reflects the platform's role as a centralized service managing credential and execution context across distributed tasks. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Prefect over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2026-5366CRITICAL 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, wh | Jun 20, 2026 | 9.9 | 40 | NO | NO |
CVE-2026-3514HIGH In version 3.6.19 of prefecthq/prefect, an authentication bypass vulnerability exists due to the improper handling of URL path exemptions for health check probes. Specifically, the | Jun 2, 2026 | 7.5 | 32 | NO | NO |
CVE-2023-6022HIGH Cross-Site Request Forgery (CSRF) in GitHub repository prefecthq/prefect prior to 2.16.5. | Nov 16, 2023 | 8.8 | 24 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Prefect.
Media articles that mention a CVE ID that affects a product developed by Prefect — matched by CVE ID, not by vendor name.