CVE-2026-3514

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-02. a secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

Published

June 2, 2026

Last Modified

July 22, 2026

Advisory Details (2)

Auto-updated Jun 6, 2026
Patch available. Sources: github_commit.
generic

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/c540e5e1-f74f-44f4-bfa0-9764ff6daa75
github_commit Patch Available

commit e21617125335 (prefecthq/prefect)

Patch available: prefecthq/prefect 3.7.1.dev1 (contains commit e21617125335)

https://github.com/prefecthq/prefect/commit/e21617125335025b4b27e7d6f0ca028e8e8f3b79

Vendor Advisories for CVE-2026-3514(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
prefect0.10.0 ... 3.6.9 (740 versions)
  • every version up to 3.6.22.dev7: fixed in 3.6.22.dev7
  • every version up to 3.6.22: fixed in 3.6.22
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 213 total refreshes for this CVE.

  1. 2026-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:12 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-06 15:17 UTCEPSS rescore
  6. 2026-10-05 17:43 UTCEPSS rescore
  7. 2026-10-04 23:22 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-03 13:09 UTCOSV refresh
  10. 2026-10-01 19:50 UTCEPSS rescore
  11. 2026-09-30 15:03 UTCEPSS rescore
  12. 2026-09-28 13:51 UTCEPSS rescore
  13. 2026-09-27 13:48 UTCEPSS rescore
  14. 2026-09-26 15:58 UTCEPSS rescore
  15. 2026-09-26 00:26 UTCEPSS rescore
  16. 2026-09-20 20:15 UTCEPSS rescore
  17. 2026-09-18 19:28 UTCEPSS rescore
  18. 2026-09-18 19:28 UTCEPSS rescore
  19. 2026-09-17 19:30 UTCEPSS rescore
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-15 03:11 UTCEPSS rescore
  23. 2026-09-14 05:50 UTCEG score recompute
  24. 2026-09-13 16:47 UTCEPSS rescore
  25. 2026-09-13 00:06 UTCOSV refresh
Show 75 more
  1. 2026-09-12 15:01 UTCEPSS rescore
  2. 2026-09-11 14:53 UTCEPSS rescore
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 09:34 UTCEPSS rescore
  5. 2026-09-08 22:00 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-04 05:06 UTCEPSS rescore
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:53 UTCEPSS rescore
  11. 2026-09-01 04:39 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:41 UTCEPSS rescore
  15. 2026-08-27 14:25 UTCEPSS rescore
  16. 2026-08-26 14:46 UTCEPSS rescore
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-25 03:46 UTCEG score recompute
  19. 2026-08-23 13:44 UTCEG score recompute
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-21 23:49 UTCEPSS rescore
  22. 2026-08-20 23:23 UTCEG score recompute
  23. 2026-08-20 22:55 UTCEPSS rescore
  24. 2026-08-20 10:12 UTCEG score recompute
  25. 2026-08-19 17:03 UTCEPSS rescore
  26. 2026-08-18 13:48 UTCEPSS rescore
  27. 2026-08-17 13:47 UTCEPSS rescore
  28. 2026-08-17 04:20 UTCEG score recompute
  29. 2026-08-16 14:56 UTCEPSS rescore
  30. 2026-08-16 04:18 UTCEG score recompute
  31. 2026-08-16 02:14 UTCEPSS rescore
  32. 2026-08-15 01:39 UTCEG score recompute
  33. 2026-08-15 01:30 UTCEPSS rescore
  34. 2026-08-13 23:17 UTCEG score recompute
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-12 14:39 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-12 01:28 UTCEG score recompute
  39. 2026-08-11 13:43 UTCEPSS rescore
  40. 2026-08-11 12:17 UTCEG score recompute
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-09 17:56 UTCEG score recompute
  43. 2026-08-09 13:46 UTCEPSS rescore
  44. 2026-08-08 02:11 UTCEG score recompute
  45. 2026-08-06 23:50 UTCEG score recompute
  46. 2026-08-06 13:46 UTCEPSS rescore
  47. 2026-08-05 20:37 UTCEG score recompute
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 19:58 UTCEG score recompute
  50. 2026-08-04 15:10 UTCEPSS rescore
  51. 2026-08-04 10:38 UTCEPSS rescore
  52. 2026-08-03 18:41 UTCEG score recompute
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 02:37 UTCEG score recompute
  55. 2026-08-02 02:27 UTCEPSS rescore
  56. 2026-08-01 13:26 UTCEG score recompute
  57. 2026-08-01 04:16 UTCEPSS rescore
  58. 2026-07-31 05:39 UTCEG score recompute
  59. 2026-07-30 16:28 UTCEPSS rescore
  60. 2026-07-30 01:30 UTCEPSS rescore
  61. 2026-07-29 10:55 UTCEG score recompute
  62. 2026-07-28 03:43 UTCEG score recompute
  63. 2026-07-27 14:13 UTCEPSS rescore
  64. 2026-07-26 22:59 UTCEG score recompute
  65. 2026-07-26 14:54 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-25 14:18 UTCEPSS rescore
  68. 2026-07-25 14:18 UTCEPSS rescore
  69. 2026-07-24 14:17 UTCEPSS rescore
  70. 2026-07-24 14:17 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 14:18 UTCEPSS rescore
  73. 2026-07-23 03:10 UTCEG score recompute
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:24 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-3514?
CVE-2026-3514 is a high vulnerability published on June 2, 2026. 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…
When was CVE-2026-3514 disclosed?
CVE-2026-3514 was first published on June 2, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3514 actively exploited?
CVE-2026-3514 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3514?
CVE-2026-3514 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-3514?
A fix for CVE-2026-3514 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-3514 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3514

Explore →

Is Your Infrastructure Affected by CVE-2026-3514?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.