CVE-2026-35167
Kedro is a toolbox for production-ready data science. Prior to …
Kedro is a toolbox for production-ready data science. Prior to 1.3.0, the _get_versioned_path() method in kedro/io/core.py constructs filesystem paths by directly interpolating user-supplied version strings without sanitization. Because version strings are used as path components, traversal sequences such as ../ are preserved and can escape the intended versioned dataset directory. This is reachable through multiple entry points: catalog.load(..., version=...), DataCatalog.from_config(..., load_versions=...), and the CLI via kedro run --load-versions=dataset:../../../secrets. An attacker who can influence the version string can force Kedro to load files from outside the intended version directory, enabling unauthorized file reads, data poisoning, or cross-tenant data access in shared environments. This vulnerability is fixed in 1.3.0.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/kedro-org/kedro/security/advisories/GHSA-6326-w46w-ppjw
- github.com/kedro-org/kedro/pull/5442
- github.com/advisories/GHSA-6326-w46w-ppjw
- nvd.nist.gov/vuln/detail/CVE-2026-35167
- github.com/pypa/advisory-database/tree/main/vulns/kedro/PYSEC-2026-71.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-35167
- cve.org/CVERecord?id=CVE-2026-35167
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.