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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.1 · linuxfoundationNVD modified 2026-10-23 23:10
Affected (CPE criteria) 1
cpe:2.3:a:linuxfoundation:kedro:*:*:*:*:*:python:*:*
References 2
- https://github.com/kedro-org/kedro/pull/5442 Issue Tracking
- https://github.com/kedro-org/kedro/security/advisories/GHSA-6326-w46w-ppjw Vendor Advisory