prefect 2.20.27
PkgFire would install this release with a warning.·Checked 6 hours ago·Published 23 October 2026
Why
-
warnVulnerability
PYSEC-2026-2261 (fixed in 3.6.22)
-
warnVulnerability
Prefect Git Argument Injection in GitRepository Pull Steps (fixed in 3.6.25.dev7)
-
warnVulnerability
Prefect Auth Bypass via endswith() Health Check Exemption (fixed in 3.6.22)
-
warnVulnerability
Prefect has an Argument Injection issue
-
warnVulnerability
Prefect Unauthenticated Event Injection via /api/events/in WebSocket (fixed in 3.6.14)
-
warnVulnerability
Prefect SSRF Bypass via DNS Rebinding in validate_restricted_url (fixed in 3.6.28.dev2)
-
warnVulnerability
Prefect Auth Bypass via endswith() Health Check Exemption (fixed in 3.6.22)
-
warnVulnerability
Prefect has an Authentication Middleware Bypass when URL paths are appended with 'health' or 'ready' (fixed in 3.6.22.dev7)
-
warnVulnerability
Prefect has an Argument Injection issue
-
warnVulnerability
Prefect Unauthenticated Event Injection via /api/events/in WebSocket (fixed in 3.6.14)
Provenance
A registry signature proves the registry served these bytes unaltered. Build provenance proves which workflow built them from which commit; a stolen publishing token can fake the first but not the second.
- Signature
- Not signed
- Build provenance
- Attested
What the code does
On its own this is weak signal: plenty of honest libraries read files or talk to the network. What PkgFire watches is a release gaining something the one before it did not.
Code reading
PkgFire's own reading of the files: what the code can do.
Source patterns
Patterns found in the source, including those malware is known to use.
Other checked releases
Check every dependency before it installs
This page is one release. PkgFire checks every package in your lockfile, on every install and in every pull request, and blocks the bad ones before they run.