CVE-2026-35167: Kedro has a path traversal in versioned dataset loading via unsanitized version string

Severity: high (CVSS 8.1 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.3% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-04-06 · updated 2026-10-23
Weakness: CWE-22

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.

Affected products

kedro-org/kedro: before 1.3.0 — fixed in 1.3.0

How to fix

Upgrade to a fixed version: kedro-org/kedro 1.3.0. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-35167 or the next vulnerability affects your stack