Products / mlflow
mlflow
87 records.
- MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifact modules On an unauthenticated MLflow server, scorer deserialisation imports a request-chosen module from an uploaded artifact and instantiates its class, running attacker code.
- MLflow CrewAI autologging records LLM provider API keys in logged trace spans MLflow autologging serializes CrewAI agent objects into trace spans, and their string form includes the LLM provider API key, which is then sent to the trace backend.
- MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source Prompt model version sources without a URL scheme skip path validation, so artifact requests can read arbitrary server files, including the auth database.
- MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints An unauthenticated endpoint instantiates a class named in JSON whose module allowlist does not constrain the class or its arguments, forcing outbound requests to attacker-chosen hosts.
- MLflow FileStore trace IDs allow path traversal and arbitrary file writes A crafted trace ID with traversal sequences, sent unauthenticated to the trace endpoint, makes the FileStore backend write metadata files outside the experiment directory.
- MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifact The statsmodels loader skips the pickle deserialisation guard, so a crafted model artifact runs code when loaded even with pickle disabled.
- MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding) Webhook delivery validates the initial URL but follows redirects without re-checking the target, letting an unauthenticated caller reach internal addresses.
- MLflow AI Gateway permits SSRF through an unvalidated api_base Gateway secrets accept an unvalidated base URL that the proxy later requests, letting any authenticated user reach internal addresses and metadata services.
- MLflow: trace API endpoints lack proper authorization validators Trace API routes skip authorization validators, so any authenticated user can read or change traces in experiments they cannot access.
- MLflow: Deterministic sampling in dataset digest enables predictable collisions Dataset digests use deterministic sampling with a weak hash, so an attacker can craft a different dataset that produces the same digest.
- MLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltration The gateway resolves environment variable references in API key fields and sends the resulting cloud credentials to an attacker-chosen upstream base URL.
- MLflow: Any authenticated user can enumerate all gateway secrets, endpoints, and model definitions Any authenticated user can call three gateway list endpoints that lack authorization handlers, retrieving all gateway secrets, endpoints and model definitions.
- MLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabled Multipart upload endpoints for artifacts skip per-resource permission checks, letting users overwrite other users' artifacts, which can later be loaded as poisoned models.
- MLflow authenticated users can enumerate any registered model versions due to lack of per-model permissions checks The model version search endpoint and GraphQL field skip per-model permission checks, so any authenticated user can list all versions and metadata.
- MLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command Execution A malicious webpage can send cross-origin requests to MLflow Assistant's local endpoints, change its settings, and then have a Claude Code sub-agent run commands.
- MLFlow Creates a Temporary File With Insecure Permissions Model artifact temp directories are created world- or group-writable, so local users can replace cloudpickle files that are later loaded and executed.
- MLflow: unauthenticated access to certain FastAPI routes Authentication is enforced only on gateway paths, so unauthenticated requests reach job and trace ingestion FastAPI routes under uvicorn.
- MLflow allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem Creating a model version with a prompt tag skips source path validation, so an unauthenticated caller can register a local path that is later served as a file.
- MLflow Has a Server-Side Request Forgery (SSRF) Vulnerability MLflow's webhook creation accepts an arbitrary URL that the backend then posts to, letting an authenticated user reach internal services and metadata endpoints.
- MLflow is vulnerable to an authorization bypass affecting the AJAX endpoint The MLflow AJAX endpoint for model artifacts skips the experiment permission check, so users without access can download artifacts directly.
- MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface Unsafe YAML parsing of MLmodel metadata lets an uploaded artifact inject script that runs in another user's browser when viewed in the UI.
- mlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization Job submission and management endpoints accept requests without credentials when basic-auth is enabled, letting any network client create and cancel jobs.
- Mlflow: Command Injection when serving models with enable_mlserver=True The model URI is interpolated unescaped into a bash -c command, so shell command substitutions inside it run when the model is served.
- MLflow Command Injection vulnerability Dependency entries in a model artifact's python_env.yaml are inserted unescaped into a shell command during local serving setup, so attacker commands run on deployment.
- MLFlow path traversal vulnerability A tar archive whose member paths contain traversal sequences is extracted without validation, so files can be written outside the target directory.
- MLFlow allows Tracing + Assessments Access Trace and assessment endpoints skip permission checks when basic auth is enabled, so any authenticated user can read traces and create assessments.
- Arbitrary file write via tar traversal in mlflow Extracting a crafted pyfunc model archive with unvalidated tar entry paths writes files outside the target directory.
- MLflow has a command injection in mlflow/sagemaker/__init__.py The sagemaker CLI interpolates the container image name into a shell command run through os.system, so shell metacharacters in the flag execute.
- MLflow Use of Default Password Authentication Bypass Vulnerability Hard-coded default credentials in the MLflow basic auth file let remote callers authenticate and reach administrator-level access.
- MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability Unauthenticated artifact requests carry unvalidated paths that escape the artifact directory, letting an attacker write files that lead to code execution as the service account.
- mlflow Creates of Temporary File in Directory with Insecure Permissions The temporary virtualenv directory is created world-writable, letting a local user race and replace Python files that later run as code.
- MLFlow is vulnerable to DNS rebinding attacks due to a lack of Origin header validation The REST server does not check the Origin header, so a DNS-rebinding page can call endpoints that read, change or delete experiments.
- MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability A model-creation request supplies an unvalidated path that allows traversal to files that lead to code execution as the service account, without authentication.
- MLflow Weak Password Requirements Authentication Bypass Vulnerability Weak password requirements let remote, unauthenticated attackers get past MLflow's authentication.
- MLFlow SSRF via gateway_proxy_handler The gateway proxy handler forwards requests with an unvalidated path, letting callers make the server reach arbitrary internal URLs.
- MLflow Uncontrolled Resource Consumption vulnerability Large batches of GraphQL queries repeatedly requesting all runs of an experiment tie up every MLflow worker, blocking other requests.
- MLflow has Weak Password Requirements Admins can create user accounts without setting a password, leaving those accounts open to anyone who can guess the username.
- MLflow has a Local File Read/Path Traversal in dbfs The dbfs URL handling checks only the path component, so traversal sequences in query or parameter parts escape the mount and read local files.
- MLflow Cross-Site Request Forgery (CSRF) vulnerability The signup endpoint accepts cross-site form submissions without anti-CSRF checks, so a third-party page can make a victim's browser create accounts.
- MLflow Uncontrolled Resource Consumption vulnerability Experiment names and artifact locations have no length limit, so oversized values make the MLflow UI hang and create resource exhaustion.
- MLflow's excessive directory permissions allow local privilege escalation Overly broad directory permissions let a local user win a race condition and escalate privileges while spark_udf runs.
- Remote code execution in mlflow Filenames taken from a remote HTTP response or URL are joined into local paths unsanitised, allowing traversal or absolute-path writes that lead to command execution.
- Undefined Behavior in mlflow URL-encoded and decoded model names are treated as different models, letting an attacker register a same-named model that users later load by mistake.
- Local File Inclusion in mlflow Directory traversal sequences placed in a URI fragment evade the validation added earlier for query strings, letting requests read arbitrary local files.
- MLFlow unsafe deserialization A malicious scikit-learn model uploaded to MLflow deserialises into code execution when a user loads and interacts with it.
- MLFlow unsafe deserialization A malicious scikit-learn model uploaded to MLflow is deserialised with pickle, so attacker code runs when the model is loaded or used.
- MLFlow unsafe deserialization A malicious serialised scikit-learn or LightGBM model uploaded to MLflow executes code when a user loads and interacts with it.
- MLFlow unsafe deserialization A maliciously crafted MLflow recipe is deserialised unsafely, so loading and running it executes attacker code.
- MLFlow unsafe deserialization A malicious LangChain AgentExecutor model uploaded to MLflow is deserialised when used, executing attacker-chosen code on the consumer's machine.
- MLFlow unsafe deserialization A malicious PyFunc model artifact is deserialised when loaded, so its embedded code runs on the machine that uses the model.