CVE-2026-0545

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 4.4% (91st percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 9.1 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-04-03) is not newer than that change (2026-08-28), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-18809 (ENISA EUVD) · GHSA-7qhf-v65m-g5f3 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 4.4%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

In mlflow/mlflow, the FastAPI job endpoints under /ajax-api/3.0/jobs/* are not protected by authentication or authorization when the basic-auth app is enabled. This vulnerability affects the latest version of the repository. If job execution is enabled (MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true) and any job function is allowlisted, any network client can submit, read, search, and cancel jobs without credentials, bypassing basic-auth entirely. This can lead to unauthenticated remote code execution if allowed jobs perform privileged actions such as shell execution or filesystem changes. Even if jobs are deemed safe, this still constitutes an authentication bypass, potentially resulting in job spam, denial of service (DoS), or data exposure in job results.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
75
EG Risk 75/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
4.4%
EPSS %ILE
91st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
4.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 3, 2026

Last Modified

August 28, 2026

Advisory Details (5)

Auto-updated Oct 31, 2026
Patch available. Sources: redhat.
Red Hat

2454889 – (CVE-2026-0545) CVE-2026-0545 mlflow/mlflow: mlflow/mlflow: Unauthenticated remote code execution via unprotected job endpoints

https://bugzilla.redhat.com/show_bug.cgi?id=2454889
Red HatMentions a patch (unverified)

CVE-2026-0545 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-0545
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:60520
Web page

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

https://huntr.com/bounties/b2e5b028-9541-4d29-8703-a76f1a3734d8

Vendor Advisories for CVE-2026-0545(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
pipmlflow—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow0.0.1 ... 3.9.0rc0 (173 versions)
  • every version through 3.10.1: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 330 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 230 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 12:59 UTCEG score recompute
  2. 2026-11-02 12:59 UTCVendor advisory
  3. 2026-11-02 12:58 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-11-01 14:52 UTCVendor advisory
  5. 2026-11-01 14:52 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-31 16:46 UTCEG score recompute
  7. 2026-10-31 16:46 UTCVendor advisory
  8. 2026-10-31 16:46 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-31 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  10. 2026-10-30 18:14 UTCEG score recompute
  11. 2026-10-30 18:14 UTCVendor advisory
  12. 2026-10-30 18:14 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-30 16:33 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  14. 2026-10-29 20:08 UTCEG score recompute
  15. 2026-10-29 20:08 UTCVendor advisory
  16. 2026-10-29 20:08 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-29 16:32 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  18. 2026-10-28 22:01 UTCEG score recompute
  19. 2026-10-28 22:01 UTCVendor advisory
  20. 2026-10-28 22:01 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-28 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  22. 2026-10-27 23:55 UTCEG score recompute
  23. 2026-10-27 23:55 UTCVendor advisory
  24. 2026-10-27 23:55 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-27 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
Show 75 more
  1. 2026-10-27 01:47 UTCEG score recompute
  2. 2026-10-27 01:47 UTCVendor advisory
  3. 2026-10-27 01:46 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  5. 2026-10-25 23:42 UTCEG score recompute
  6. 2026-10-25 23:42 UTCVendor advisory
  7. 2026-10-25 23:41 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  9. 2026-10-25 15:58 UTCEG score recompute
  10. 2026-10-25 01:21 UTCEG score recompute
  11. 2026-10-25 01:21 UTCVendor advisory
  12. 2026-10-25 01:21 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-24 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  14. 2026-10-24 03:15 UTCEG score recompute
  15. 2026-10-24 03:15 UTCVendor advisory
  16. 2026-10-24 03:15 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-23 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  18. 2026-10-23 05:08 UTCEG score recompute
  19. 2026-10-23 05:08 UTCVendor advisory
  20. 2026-10-23 05:08 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-22 16:33 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  22. 2026-10-22 06:59 UTCEG score recompute
  23. 2026-10-22 06:59 UTCVendor advisory
  24. 2026-10-22 06:59 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-21 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  26. 2026-10-21 08:52 UTCEG score recompute
  27. 2026-10-21 08:52 UTCVendor advisory
  28. 2026-10-21 08:52 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-20 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  30. 2026-10-20 10:46 UTCEG score recompute
  31. 2026-10-20 10:46 UTCVendor advisory
  32. 2026-10-20 10:46 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-19 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  34. 2026-10-19 12:37 UTCEG score recompute
  35. 2026-10-19 12:37 UTCVendor advisory
  36. 2026-10-19 12:37 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-18 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  38. 2026-10-18 10:56 UTCVendor advisory
  39. 2026-10-18 10:56 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  40. 2026-10-18 05:12 UTCEG score recompute
  41. 2026-10-17 16:33 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  42. 2026-10-17 12:49 UTCEG score recompute
  43. 2026-10-17 12:49 UTCVendor advisory
  44. 2026-10-17 12:48 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  45. 2026-10-16 16:40 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  46. 2026-10-16 14:40 UTCEG score recompute
  47. 2026-10-16 14:40 UTCVendor advisory
  48. 2026-10-16 14:40 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  49. 2026-10-15 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  50. 2026-10-15 15:45 UTCEG score recompute
  51. 2026-10-15 15:45 UTCVendor advisory
  52. 2026-10-15 15:45 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  53. 2026-10-14 16:31 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  54. 2026-10-14 09:58 UTCEG score recompute
  55. 2026-10-14 09:58 UTCVendor advisory
  56. 2026-10-14 09:58 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  57. 2026-10-13 16:33 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  58. 2026-10-13 08:02 UTCVendor advisory
  59. 2026-10-13 08:02 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  60. 2026-10-12 16:42 UTCEG score recompute
  61. 2026-10-12 16:33 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  62. 2026-10-12 09:55 UTCVendor advisory
  63. 2026-10-12 09:55 UTCGHSA enrichmentGHSA-7qhf-v65m-g5f3 · GitHub severity CRITICAL · GitHub CVSS 9.1
  64. 2026-10-11 20:17 UTCEG score recompute
  65. 2026-10-11 18:29 UTCEG score recompute
  66. 2026-10-11 15:03 UTCEG score recompute
  67. 2026-10-11 13:47 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  68. 2026-10-10 19:59 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  69. 2026-10-09 20:06 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  70. 2026-10-08 17:11 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  71. 2026-10-07 23:47 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  72. 2026-10-06 15:17 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  73. 2026-10-05 17:42 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  74. 2026-10-03 14:25 UTCEPSS rescoreEPSS 4.4% · 91st percentile
  75. 2026-10-01 19:49 UTCEPSS rescoreEPSS 4.4% · 91st percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-0545.yaml
    Published May 5, 2026

    MLflow Job API - Authentication Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2026-0545?
CVE-2026-0545 is a critical-severity vulnerability; its CVE record was published on April 3, 2026. In mlflow/mlflow, the FastAPI job endpoints under /ajax-api/3.0/jobs/* are not protected by authentication or authorization when the basic-auth app is enabled. This vulnerability affects the latest version of the repository. If job execution is enabled (MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true) and…
When was the CVE record for CVE-2026-0545 published?
The CVE record for CVE-2026-0545 was published on April 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-0545 actively exploited?
CVE-2026-0545 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.4% probability of exploitation in the next 30 days (91st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-0545?
CVE-2026-0545 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-0545?
A fix for CVE-2026-0545 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-0545 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-0545

Explore →

Is Your Infrastructure Affected by CVE-2026-0545?

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