evidentlyai Evidently up to 0.7.21 Dataset Materialization Endpoint filename path traversal

Summaryinfo

A vulnerability was found in evidentlyai Evidently up to 0.7.21. It has been classified as problematic. The impacted element is an unknown function of the component Dataset Materialization Endpoint. Performing a manipulation of the argument filename results in path traversal. This vulnerability is identified as CVE-2026-75111. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in evidentlyai Evidently up to 0.7.21. This affects an unknown code block of the component Dataset Materialization Endpoint. The manipulation of the argument filename with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on confidentiality. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-75111 since 08/17/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/17/2026). The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• evidentlyai

Name

• Evidently

Version

• 0.7.0
• 0.7.1
• 0.7.2
• 0.7.3
• 0.7.4
• 0.7.5
• 0.7.6
• 0.7.7
• 0.7.8
• 0.7.9
• 0.7.10
• 0.7.11
• 0.7.12
• 0.7.13
• 0.7.14
• 0.7.15
• 0.7.16
• 0.7.17
• 0.7.18
• 0.7.19
• 0.7.20
• 0.7.21

Website

• Product: https://github.com/evidentlyai/evidently/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion