Authorization Flaw in prefect (CVE-2026-3514)
Summary
Vulnerability in prefect (CVE-2026-3514). Confidential information can be exposed externally. Mitigation: upgrade to 3.6.22.dev7 or later.
Original description
The description as published by the source.
In version 3.6.19 of prefecthq/prefect, an authentication bypass vulnerability exists due to the improper handling of URL path exemptions for health check probes. Specifically, the authentication middleware exempts any URL path ending with 'health' or 'ready' from authentication checks. This allows an attacker to create resources with names ending in 'health' or 'ready' and access them without authentication. Affected endpoints include those for variables, flows, work pools, work queues, and deployments. This vulnerability can lead to unauthorized access to sensitive information, such as API keys and database credentials, stored in Prefect Variables.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-3514 has been found in prefect.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade prefect to 3.6.22.dev7 or later.
If unsure, ask your IT team or search "prefect CVE-2026-3514" on the vendor's site.
CVE-2026-3514 (prefect) — CWE-863 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.6.22.dev7 — 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.
Incorrect authorization (CWE-863) exists in prefect.
Check the vendor advisory for the affected versions of prefect.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 3.6.22.dev7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade prefect to 3.6.22.dev7ステージング環境で 3.6.22.dev7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- patch github.com
- web huntr.com
- web github.com