{"answers":{"affected":"3 open source packages ship an affected version, including prefect. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3514 exists.","fix":"Upgrade prefect to a fixed version for your release line: 3.6.22 or 3.6.22.dev7.","what":"CVE-2026-3514 is a high-severity authentication bypass vulnerability in prefecthq/prefect, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3514 and fix it if it is affected.\n\nWhat it is: CVE-2026-3514 is a high-severity authentication bypass vulnerability in prefecthq/prefect, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3514 exists.\n\nAffected packages and fixed versions:\n- prefect (PyPI): affected all versions; fixed in 3.6.22\n- prefect (PyPI): affected all versions; fixed in 3.6.22.dev7\n- prefect (PyPI): affected all versions; fixed in 3.6.22.dev7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3514/ (Markdown: https://insights.sbomify.com/CVE-2026-3514/index.md)","id":"CVE-2026-3514","markdown":"https://insights.sbomify.com/CVE-2026-3514/index.md","name":"CVE-2026-3514","record":{"aliases":["GHSA-c635-393c-hcx2","PYSEC-2026-2261","ROOT-APP-PYPI-CVE-2026-3514"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Workflow orchestration platform","requires_auth":"none","summary":"Attackers can bypass authentication by accessing endpoints with names ending in 'health' or 'ready', exposing sensitive data like API keys.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"prefect","vendor":"prefect"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Authentication Bypass in prefecthq/prefect","id":"CVE-2026-3514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Argument Injection in prefecthq/prefect","id":"CVE-2026-3515"},"packages":[{"ecosystem":"PyPI","fixed":["3.6.22"],"introduced":["0"],"last_affected":[],"package":"prefect","purl":"pkg:pypi/prefect","source":"PYSEC-2026-2261"},{"ecosystem":"PyPI","fixed":["3.6.22.dev7"],"introduced":["0"],"last_affected":[],"package":"prefect","purl":null,"source":"GHSA-c635-393c-hcx2"},{"ecosystem":"PyPI","fixed":["3.6.22.dev7"],"introduced":["0"],"last_affected":[],"package":"prefect","purl":"pkg:pypi/prefect","source":"GHSA-c635-393c-hcx2"}],"prev":{"headline":"Cross-site scripting in TableOn – WordPress Posts Table Filterable","id":"CVE-2026-3513"},"products":["prefecthq/prefect"],"published":"2026-06-02","related":[{"cvss_score":9.9,"headline":"Git Argument Injection in prefecthq/prefect","id":"CVE-2026-5366","kev_date_added":null,"published":"2026-06-20"},{"cvss_score":8.8,"headline":"Cross-Site Request Forgery (CSRF) in prefecthq/prefect","id":"CVE-2023-6022","kev_date_added":null,"published":"2023-11-16"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-02","vendors":["prefecthq"]},"summary":"Attackers can bypass authentication by accessing endpoints with names ending in 'health' or 'ready', exposing sensitive data like API keys.","url":"https://insights.sbomify.com/CVE-2026-3514/"}