CVE-2026-7722 in prefect
Summary
by MITRE • 05/04/2026
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. Upgrading the affected component is recommended.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 05/08/2026
The vulnerability identified in PrefectHQ prefect version 3.6.21 and earlier represents a critical authentication flaw within the Health Check API component that exposes the system to remote exploitation. This issue specifically affects the endswith function implementation in the /api/health endpoint, where improper input validation allows attackers to manipulate authentication flows. The vulnerability's classification aligns with CWE-284 Access Control Issues and CWE-312 Cleartext Storage of Sensitive Information, as it enables unauthorized access through flawed authentication mechanisms. The remote exploitability means that attackers can leverage this weakness without requiring physical access or local network presence, making it particularly dangerous in cloud and distributed environments where such APIs are frequently exposed to external traffic.
The technical exploitation of this vulnerability occurs through manipulation of the endswith function within the health check API, which likely processes user input or system identifiers that should be properly validated before authentication decisions are made. This flaw allows attackers to bypass authentication mechanisms by crafting specific inputs that exploit the improper handling of string matching operations. The attack vector demonstrates characteristics consistent with CWE-20 Improper Input Validation, where the system fails to properly validate or sanitize inputs before processing them in authentication contexts. The public availability of exploit code significantly increases the risk surface, as it removes the need for advanced technical skills to carry out the attack, making this vulnerability particularly dangerous for organizations running affected versions.
The operational impact of this vulnerability extends beyond simple unauthorized access, as it can enable attackers to gain insights into system health status, potentially exposing sensitive operational information that could be used for further attacks. Organizations relying on Prefect's health check functionality may experience complete compromise of their orchestration systems, as the health API endpoint often serves as a critical monitoring interface that attackers can leverage for reconnaissance and privilege escalation. The vulnerability affects systems where Prefect is deployed in production environments, potentially compromising workflows, data integrity, and overall system availability. This flaw particularly impacts organizations using cloud-native deployment models where health check endpoints are frequently exposed to external networks and may be subject to automated scanning and exploitation.
Mitigation strategies should prioritize immediate upgrading to version 3.6.22 or later, which contains the necessary patches to address the authentication bypass vulnerability. Organizations should also implement network segmentation to limit access to health check endpoints, particularly those exposed externally. Additional defensive measures include implementing API rate limiting, monitoring for unusual patterns in health check requests, and conducting thorough security assessments of all API endpoints. The remediation process should include validating that the upgrade has properly addressed the vulnerability through penetration testing and security scanning. Organizations should also review their access control policies for health check endpoints and consider implementing additional authentication layers or API gateways that can provide additional protection against similar vulnerabilities. Compliance with security standards such as NIST SP 800-53 and ISO 27001 requires regular vulnerability assessments and prompt remediation of identified security flaws.