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

> Unauthenticated attackers can read arbitrary system files via path traversal in the dataset materialization filename parameter.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-cjrm-54c2-4w78

## What is CVE-2026-75111?

CVE-2026-75111 is a high-severity path traversal vulnerability in evidentlyai evidently, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-75111?


## How do I fix CVE-2026-75111?

No fix has been published for CVE-2026-75111 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75111 being exploited?

There is no known exploitation of CVE-2026-75111 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75111 and fix it if it is affected.

What it is: CVE-2026-75111 is a high-severity path traversal vulnerability in evidentlyai evidently, published on 17 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-75111 in the wild and no public exploit code.

Affected product: evidentlyai evidently. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75111/ (Markdown: https://insights.sbomify.com/CVE-2026-75111/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75111
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75111
- OSV: https://osv.dev/vulnerability/CVE-2026-75111

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75111/
Summaries are generated and may contain mistakes; the official description above is the record.