Security readout for executives and security teams
Plain-English summary
MLflow deployments can expose job-management functions without credentials even when basic authentication is enabled. Under the vulnerable configuration, reachable outsiders may manipulate jobs and potentially execute code when permitted jobs perform privileged actions. The supplied evidence does not identify a complete affected-version range.
Executive priority
Treat reachable deployments meeting all configuration prerequisites as an immediate containment and remediation priority. Determine whether allowed jobs can perform privileged actions or expose sensitive results. Isolate affected services first, then follow vendor guidance for permanent remediation. Deployments without job execution enabled are not described as exploitable through this path.
Technical view
FastAPI endpoints under `/ajax-api/3.0/jobs/*` bypass authentication and authorization with the basic-auth app enabled. Exposure requires `MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true` and at least one allowlisted job function. Network clients can submit, read, search, and cancel jobs without credentials. The issue is classified as CWE-306 with CVSS 9.1.
Likely exposure
Risk is highest for internet-facing or broadly reachable MLflow servers using basic-auth with job execution enabled and allowlisted functions. Remote code execution depends on what those functions can do. Other exposed deployments may still face unauthorized job operations, result disclosure, resource exhaustion, or service disruption.
Exploitation context
The source bundle states that this CVE is not in KEV, and the supplied evidence does not establish active exploitation. Exploitation requires network access to the MLflow service and the identified job-execution configuration; no credentials or user interaction are required.
Researcher notes
The record says the latest repository version is affected but lists versions as unspecified, limiting precise asset matching. The CVSS vector records no availability impact, while the description identifies job spam and denial-of-service potential. The supplied material does not name an MLflow fixed version or demonstrate exploitation in the wild.
Mitigation direction
- Disable MLflow job execution until vendor-confirmed remediation is applied.
- Remove all allowlisted job functions if job execution is unnecessary.
- Restrict MLflow network access to trusted administrative clients and management networks.
- Consult MLflow guidance and the applicable Red Hat advisory for fixed packages or supported remediation.
- Prioritize deployments where allowed jobs can execute shells, modify files, or access sensitive data.
Validation and detection
- Inventory MLflow instances, versions, authentication mode, job-execution setting, and allowlisted functions.
- Confirm the job endpoints reject unauthenticated requests in an authorized test environment.
- Verify network controls prevent untrusted clients from reaching MLflow.
- Review available job records and service logs for unexpected submissions, reads, searches, or cancellations.
- Confirm remediation against vendor guidance because the sources omit a complete affected-version range.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-306: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0545 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.0)
- Known Exploited
- No
- Published
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2@huntr_aiCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Base CVSS 3.0 score
9.1CriticalVector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-04-03T18:01:06.806Z: Reported to Red Hat.
- 2026-04-03T17:03:12.833Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://huntr.com/bounties/b2e5b028-9541-4d29-8703-a76f1a3734d8CVE reference, @huntr_ai
- https://access.redhat.com/security/cve/CVE-2026-0545CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2454889CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-0545.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:60520CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Missing Authentication for Critical Function
Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.