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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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%
Action: Remediate soon — notable exploitation risk.
EPSS
38.3%
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 rangeFixed inDependents
prefect0.10.0 ... 3.6.9 (738 versions)3.6.22.dev7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 53× 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 116 total refreshes for this CVE.

  1. 2026-07-23 03:10 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 17:03 UTCEPSS rescore
  9. 2026-07-15 16:57 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 02:00 UTCEPSS rescore
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 06:13 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-09 07:37 UTCGHSA enrichment
  19. 2026-07-08 16:43 UTCGHSA enrichment
  20. 2026-07-08 15:15 UTCEPSS rescore
  21. 2026-07-07 13:46 UTCEPSS rescore
  22. 2026-07-06 16:27 UTCEPSS rescore
  23. 2026-07-06 16:27 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-06 02:23 UTCEPSS rescore
Show 75 more
  1. 2026-07-05 02:30 UTCEPSS rescore
  2. 2026-07-04 06:31 UTCEPSS rescore
  3. 2026-07-04 00:10 UTCGHSA enrichment
  4. 2026-07-02 14:57 UTCGHSA enrichment
  5. 2026-07-02 01:42 UTCGHSA enrichment
  6. 2026-07-01 15:06 UTCEPSS rescore
  7. 2026-07-01 12:05 UTCGHSA enrichment
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-30 22:54 UTCGHSA enrichment
  10. 2026-06-30 00:26 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 11:15 UTCGHSA enrichment
  13. 2026-06-28 20:15 UTCGHSA enrichment
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 07:03 UTCGHSA enrichment
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 17:51 UTCGHSA enrichment
  18. 2026-06-27 04:39 UTCGHSA enrichment
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-26 15:26 UTCGHSA enrichment
  21. 2026-06-25 17:06 UTCGHSA enrichment
  22. 2026-06-25 13:49 UTCEPSS rescore
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 03:54 UTCGHSA enrichment
  25. 2026-06-24 14:42 UTCGHSA enrichment
  26. 2026-06-24 14:05 UTCEPSS rescore
  27. 2026-06-23 23:30 UTCGHSA enrichment
  28. 2026-06-23 21:33 UTCEPSS rescore
  29. 2026-06-22 14:25 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-21 14:56 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 01:59 UTCEPSS rescore
  34. 2026-06-20 13:15 UTCGHSA enrichment
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-18 21:42 UTCGHSA enrichment
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-18 07:54 UTCGHSA enrichment
  40. 2026-06-17 17:58 UTCGHSA enrichment
  41. 2026-06-17 17:53 UTCEPSS rescore
  42. 2026-06-17 04:43 UTCGHSA enrichment
  43. 2026-06-16 17:52 UTCEPSS rescore
  44. 2026-06-16 15:23 UTCGHSA enrichment
  45. 2026-06-16 02:10 UTCGHSA enrichment
  46. 2026-06-15 17:49 UTCEPSS rescore
  47. 2026-06-15 12:59 UTCGHSA enrichment
  48. 2026-06-14 23:47 UTCGHSA enrichment
  49. 2026-06-14 10:35 UTCGHSA enrichment
  50. 2026-06-13 23:00 UTCEPSS rescore
  51. 2026-06-13 21:24 UTCGHSA enrichment
  52. 2026-06-13 08:12 UTCGHSA enrichment
  53. 2026-06-12 23:12 UTCEPSS rescore
  54. 2026-06-12 23:12 UTCEPSS rescore
  55. 2026-06-12 19:00 UTCGHSA enrichment
  56. 2026-06-12 05:49 UTCGHSA enrichment
  57. 2026-06-11 16:38 UTCGHSA enrichment
  58. 2026-06-11 14:00 UTCEPSS rescore
  59. 2026-06-11 03:26 UTCGHSA enrichment
  60. 2026-06-10 22:18 UTCEPSS rescore
  61. 2026-06-10 14:15 UTCGHSA enrichment
  62. 2026-06-10 13:22 UTCEPSS rescore
  63. 2026-06-10 01:04 UTCGHSA enrichment
  64. 2026-06-09 11:53 UTCGHSA enrichment
  65. 2026-06-08 22:43 UTCGHSA enrichment
  66. 2026-06-08 14:17 UTCEPSS rescore
  67. 2026-06-08 14:17 UTCEPSS rescore
  68. 2026-06-08 09:31 UTCGHSA enrichment
  69. 2026-06-07 20:21 UTCGHSA enrichment
  70. 2026-06-07 15:25 UTCEPSS rescore
  71. 2026-06-07 15:25 UTCEPSS rescore
  72. 2026-06-07 15:25 UTCEPSS rescore
  73. 2026-06-07 07:10 UTCGHSA enrichment
  74. 2026-06-06 17:59 UTCGHSA enrichment
  75. 2026-06-06 13:47 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 in the National Vulnerability Database 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 38.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-3514?
CVE-2026-3514 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-3514?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3514, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs