Kedro has a path traversal in versioned dataset loading via unsanitized version string
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-35167
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 01:33 UTC · Revision 1
Source evidence
Kedro has a path traversal in versioned dataset loading via unsanitized version string
core-osv · Original sourcePublished 6 Apr 2026, 17:43 UTC
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.
osv:CVE-2026-35167
Complete source record
{
"id": "dcf85f10c7ec6df062715a271bee70835cec70bb46dfcc6ff03f2bd3732c8e87",
"url": "https://osv.dev/vulnerability/CVE-2026-35167",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Kedro has a path traversal in versioned dataset loading via unsanitized version string",
"summary": "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.",
"evidence": "osv:CVE-2026-35167",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-35167",
"aliases": [
"CVE-2026-35167",
"GHSA-6326-w46w-ppjw",
"PYSEC-2026-71"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/kedro-org/kedro",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "d1af1822687a438a0f3fba8913a919d06e02c298"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.3.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"cpe": "cpe:2.3:a:linuxfoundation:kedro:*:*:*:*:*:python:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.3.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"1.2.0",
"1.1.1",
"1.1.0",
"0.19.14",
"1.0.0",
"1.0.0rc3",
"1.0.0rc2",
"1.0.0rc1",
"0.19.13",
"0.19.12",
"0.19.11",
"0.19.10",
"0.19.9",
"0.19.8",
"0.19.7",
"0.19.6",
"0.19.0",
"0.19.1",
"0.19.2",
"0.19.3",
"0.19.4",
"0.19.5",
"0.18.14",
"0.18.13",
"0.18.12",
"0.18.11",
"0.18.10",
"0.18.9",
"0.18.8",
"0.18.7",
"0.18.6",
"0.18.5",
"0.18.4",
"0.18.3",
"0.18.2",
"0.18.1",
"0.18.0",
"0.17.7",
"0.17.6",
"0.17.5",
"0.17.4",
"0.17.3",
"0.17.2",
"0.17.1",
"0.17.0",
"0.16.6",
"0.16.5",
"0.16.4",
"0.16.3",
"0.16.2",
"0.16.1",
"0.16.0",
"0.15.9",
"0.15.8",
"0.15.7",
"0.15.6",
"0.15.5",
"0.15.4",
"0.15.3",
"0.15.2",
"0.15.1",
"0.15.0",
"0.14.3",
"0.14.2",
"0.14.1",
"0.14.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-35167.json"
}
}
],
"modified": "2026-10-28T02:30:24.977931097Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/35xxx/CVE-2026-35167.json",
"https://github.com/kedro-org/kedro/security/advisories/GHSA-6326-w46w-ppjw",
"https://nvd.nist.gov/vuln/detail/CVE-2026-35167",
"https://github.com/kedro-org/kedro/pull/5442"
],
"provider_metadata": {
"cwe_ids": [
"CWE-22"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/35xxx/CVE-2026-35167.json"
}
},
"related_cves": [
{
"value": "CVE-2026-35167",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 491647,
"published_at": "2026-04-06T17:43:21.922+00:00"
}