CVE-2026-7722: PrefectHQ prefect Health Check API health endswith improper authentication
A vulnerability was detected in PrefectHQ prefect up to 3.6.21. This impacts the function endswith of the file /api/health of the component Health Check API. Performing a manipulation results in improper authentication. The attack is possible to be carried out remotely. The exploit is now public and may be used. Upgrading to version 3.6.22 will fix this issue. The patch is named e21617125335025b4b27e7d6f0ca028e8e8f3b79. Upgrading the affected component is recommended. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
PrefectHQ prefect (Health Check API)to a version that resolves this vulnerability.Fixed in 3.6.22Patch e21617125335025b4b27e7d6f0ca028e8e8f3b79
Event History
Frequently Asked Questions
What is the severity of CVE-2026-7722?
CVE-2026-7722 is classified as a high severity vulnerability due to improper authentication in the Health Check API.
How do I fix CVE-2026-7722?
To fix CVE-2026-7722, upgrade to PrefectHQ prefect version 3.6.22 or later, which addresses the authentication issue.
What component is affected by CVE-2026-7722?
CVE-2026-7722 impacts the Health Check API, specifically the function endswith in the /api/health endpoint.
What are the potential consequences of CVE-2026-7722?
Exploitation of CVE-2026-7722 can lead to unauthorized access and manipulation of the Health Check API.
Is CVE-2026-7722 present in older versions of PrefectHQ prefect?
Yes, CVE-2026-7722 affects all versions of PrefectHQ prefect up to and including 3.6.21.