CVE-2026-3514: CWE-863 Incorrect Authorization in prefecthq prefecthq/prefect
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.
AI Analysis
Technical Summary
In prefecthq/prefect version 3.6.19, an incorrect authorization vulnerability (CWE-863) exists due to improper handling of URL path exemptions in the authentication middleware. Paths ending with 'health' or 'ready' are excluded from authentication, allowing attackers to bypass authentication by naming resources with these suffixes. This affects multiple endpoints including variables, flows, work pools, work queues, and deployments, potentially exposing sensitive data such as API keys and database credentials stored in Prefect Variables. The vulnerability is rated high severity with a CVSS 3.0 score of 7.5. No patch or official remediation level has been disclosed as of the published date.
Potential Impact
The vulnerability allows unauthenticated attackers to access sensitive endpoints by exploiting the authentication bypass for URL paths ending with 'health' or 'ready'. This can lead to unauthorized disclosure of sensitive information, including API keys and database credentials stored within Prefect Variables. There is no indication of impact on integrity or availability, and no known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid naming resources with suffixes 'health' or 'ready' and restrict access to Prefect endpoints through network controls or other compensating controls to reduce exposure.
CVE-2026-3514: CWE-863 Incorrect Authorization in prefecthq prefecthq/prefect
Description
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.
CVSS v3.0
Score 7.5high
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In prefecthq/prefect version 3.6.19, an incorrect authorization vulnerability (CWE-863) exists due to improper handling of URL path exemptions in the authentication middleware. Paths ending with 'health' or 'ready' are excluded from authentication, allowing attackers to bypass authentication by naming resources with these suffixes. This affects multiple endpoints including variables, flows, work pools, work queues, and deployments, potentially exposing sensitive data such as API keys and database credentials stored in Prefect Variables. The vulnerability is rated high severity with a CVSS 3.0 score of 7.5. No patch or official remediation level has been disclosed as of the published date.
Potential Impact
The vulnerability allows unauthenticated attackers to access sensitive endpoints by exploiting the authentication bypass for URL paths ending with 'health' or 'ready'. This can lead to unauthorized disclosure of sensitive information, including API keys and database credentials stored within Prefect Variables. There is no indication of impact on integrity or availability, and no known exploits have been reported in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, users should avoid naming resources with suffixes 'health' or 'ready' and restrict access to Prefect endpoints through network controls or other compensating controls to reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- @huntr_ai
- Date Reserved
- 2026-03-04T15:03:15.653Z
- Cvss Version
- 3.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a1e9560e29bf47b50adbe60
Added to database: 6/2/2026, 8:33:36 AM
Last enriched: 6/2/2026, 9:03:28 AM
Last updated: 6/3/2026, 5:04:11 AM
Views: 5
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.