Vulnerability Description
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.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Linuxfoundation | Kedro | < 1.3.0 |
Related Weaknesses (CWE)
References
- https://github.com/kedro-org/kedro/pull/5442Issue Tracking
- https://github.com/kedro-org/kedro/security/advisories/GHSA-6326-w46w-ppjwVendor Advisory
FAQ
What is CVE-2026-35167?
CVE-2026-35167 is a vulnerability with a CVSS score of 7.1 (HIGH). 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 s...
How severe is CVE-2026-35167?
CVE-2026-35167 has been rated HIGH with a CVSS base score of 7.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-35167?
Check the references section above for vendor advisories and patch information. Affected products include: Linuxfoundation Kedro.