CVE-2026-75111 in Evidently
Summary
by MITRE • 08/18/2026
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.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 08/18/2026
The vulnerability identified in Evidently UI represents a critical path traversal flaw within the dataset materialization functionality, specifically affecting how the application handles user-supplied input for file paths. This issue stems from an insufficient validation mechanism applied to the filename parameter during the data processing workflow. When users or automated systems request specific files to be included in a dataset for analysis, the backend service accepts these filenames without adequately sanitizing them against directory traversal sequences such as dot-dot-slash (../) or absolute path specifications like /etc/passwd on Linux-based systems. This lack of rigorous input validation allows an attacker to manipulate the file resolution logic, causing the application to access and serve files located outside the intended workspace directory boundaries.
From a technical perspective, this flaw is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which falls within the broader category of path traversal vulnerabilities. The operational impact is severe because it enables unauthenticated attackers to read arbitrary system files that should remain inaccessible. By supplying carefully crafted filenames containing relative or absolute paths pointing to sensitive configuration files, environment variables, source code, or other confidential data stored on the server hosting Evidently UI, an attacker can exfiltrate this information through the download endpoint. The materialization process effectively acts as a conduit, converting these restricted system resources into downloadable dataset formats that are then served back to the requester without restriction.
This vulnerability aligns with several techniques observed in malicious campaigns and is mapped to ATT&CK technique T1083: File and Directory Discovery, where adversaries search for sensitive information on compromised systems. Furthermore, it relates to CWE-209: Generation of Error Message Containing Sensitive Information if the error responses reveal details about the file system structure during failed access attempts. The ability to bypass directory restrictions undermines the fundamental security principle of least privilege and isolation between user data and system resources. In a multi-tenant or shared hosting environment, this could lead to cross-user data leakage, compromising the confidentiality of other users' projects and sensitive organizational assets stored on the same server infrastructure.
Mitigation strategies must focus on implementing strict input validation at both the client and server sides. The application should enforce allowlisting for file extensions and reject any filename containing path traversal characters or absolute paths before processing begins. Additionally, employing canonicalization techniques to resolve all symbolic links and relative references early in the request lifecycle can help detect attempts to escape the designated directory root. Security controls such as chroot jails or containerized environments with restricted filesystem access provide an additional layer of defense by limiting what files are visible even if traversal is attempted. Regular security audits and static code analysis focused on file I/O operations are recommended to identify similar weaknesses in other endpoints within the Evidently UI ecosystem, ensuring comprehensive protection against path-based attacks.