Quick answers
- Is CVE-2026-7722 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7722 being exploited in the wild.
- How severe is CVE-2026-7722?
- Medium severity, with a CVSS score of 5.3, published 4 May 2026.
- Which products and versions are affected?
- prefect (PyPI) < 3.6.22, ECOSYSTEM:introduced=0,fixed=3.6.22.
- Is there a fix for CVE-2026-7722?
- Yes. prefect (PyPI): upgrade to 3.6.22 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-7722 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7722?
- Check whether you run prefect (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- prefect (PyPI): upgrade to 3.6.22 or later
pip install "prefect>=3.6.22"
Technical details
An authentication bypass vulnerability exists in Prefect versions prior to 3.6.22 due to an improper implementation of health check exemptions. The vulnerability is located in the `/api/health` component, specifically involving the `endswith()` function used to identify exempt paths. An attacker can manipulate requests to satisfy this string comparison, allowing them to bypass authentication requirements. This is a remote, unauthenticated attack that can result in unauthorized access to health check data. The issue is addressed in version 3.6.22.
Affected products
- PrefectHQ prefect < 3.6.22
Identifiers
- CVE-2026-7722
- GHSA-6rr6-v7cj-mxpg
- PYSEC-2026-2956
Timeline
- 2026-05-04: advisory
- 2026-05-04: disclosed
- 2026-05-22: patched