← Back
CVE-2026-7722
Authentication Bypass in prefect (CVE-2026-7722)
Summary
authentication bypass in prefect (CVE-2026-7722). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `3.6.22` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-7722** has been found in prefect.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade prefect to **3.6.22** or later.
If unsure, ask your IT team or search "prefect CVE-2026-7722" on the vendor's site.
CVE-2026-7722 (prefect) — CWE-287 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `3.6.22` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**authentication bypass** (CWE-287) exists in prefect.
📍 Affected scope
prefect — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.6.22**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'prefect' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'prefect' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `prefect` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade prefect to 3.6.22ステージング環境で 3.6.22 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
prefect
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.22"}]}]
PyPI
prefect
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.6.22"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-7722
- package https://github.com/PrefectHQ/prefect
- web https://github.com/PrefectHQ/prefect/pull/21063
- web https://github.com/PrefectHQ/prefect/pull/21063/changes/d8c4ff97ef7c0a940925d32b2d76324c8def42de
- web https://gist.github.com/nedlir/f576abbb0e491dc9bb7e106c140dda04
- web https://github.com/PrefectHQ/prefect/releases/tag/3.6.22
- web https://vuldb.com/submit/807255
- web https://vuldb.com/vuln/360898
- web https://vuldb.com/vuln/360898/cti
- web https://github.com/PrefectHQ/prefect/commit/e21617125335025b4b27e7d6f0ca028e8e8f3b79
- web https://github.com/advisories/GHSA-6rr6-v7cj-mxpg