

Prefect 3.9.4, released November 19, includes two useful boundary checks: explicit validation of the UI’s post-login destination and a server-side rule preventing a stale worker from moving a completed flow run back to Pending.
These are distinct fixes. One concerns navigation after authentication; the other concerns the state a distributed worker is allowed to propose. Combining them into a generic claim of improved security or exactly-once execution would lose the important details.
A login destination must remain a local path
The redirect change validates that a value starts as a path and remains on the same origin under URL parsing. Invalid or unparseable values are dropped so login can fall back to the dashboard.
The patch uses two placeholder origins in the check. A relative path preserves each origin; a network-path reference resolves to its own host and cannot match both. That makes the intended restriction explicit rather than depending entirely on the router’s existing behavior.
The contributor’s explanation says the router already kept the current values on the same origin. This is therefore a report of added validation, not evidence that an exploitable redirect incident occurred. We have not conducted a penetration test or established a CVE.
Completed work should not become pending through an old poll
The worker-state fix rejects a Completed-to-Pending proposal at the server. Its explanation identifies a case in which a worker retained an older copy of a run after another worker had completed it without persisted result data.
The change does not ban all reruns. The source notes distinguish scheduled reruns, ad hoc execution and forced transitions. It does not establish an exactly-once guarantee for external actions performed by a flow.
Our analysis: enforce the rule where the decision is made
A refreshed worker-side view can become stale again before the server acts. Checking the transition against the server’s locked run state puts the rule at the point where it matters. That is a stronger way to reason about this particular race than assuming frequent polling eliminates it.
The navigation change follows a related principle. An application can state its own accepted destination contract even when a dependency currently behaves safely. Keeping that contract visible makes it easier to evaluate future changes and invalid inputs.
Our Prefect repository profile links the Apache-2.0 implementation. Hosted Prefect services have separate access arrangements. We reviewed release notes, both patches and their stated test cases; we did not install the update, run a workflow or execute the upstream tests.
EXPLORE THE SOURCE
Projects in this story
GitHub repositories
- PrefectHQ/prefect ↗View project details
Primary-source review and original editorial analysis. No software installation, model inference, paid service call, security validation or independent benchmark performed.



