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

> Attackers can manipulate version strings to read or modify files outside the intended dataset directory in Kedro data science projects.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-6326-w46w-ppjw, PYSEC-2026-71

## What is CVE-2026-35167?

CVE-2026-35167 is a high-severity path traversal vulnerability in kedro-org kedro, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-35167?

3 open source packages ship an affected version, including kedro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kedro` | PyPI | All versions | 1.3.0 |
| `kedro` | PyPI | All versions | 1.3.0 |
| `kedro` | PyPI | All versions | 1.3.0 |

Products: Linuxfoundation Kedro.

## How do I fix CVE-2026-35167?

Upgrade kedro to 1.3.0 or later.

## Is CVE-2026-35167 being exploited?

There is no known exploitation of CVE-2026-35167 in the wild and no public exploit code.

## Other vulnerabilities in kedro-org kedro

- [CVE-2026-35171](https://insights.sbomify.com/CVE-2026-35171/): Arbitrary Code Execution via Malicious Logging Configuration in Kedro (critical 9.8)
- [CVE-2026-3840](https://insights.sbomify.com/CVE-2026-3840/): Path Traversal in kedro-org/kedro (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35167 and fix it if it is affected.

What it is: CVE-2026-35167 is a high-severity path traversal vulnerability in kedro-org kedro, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35167 in the wild and no public exploit code.

Affected packages and fixed versions:
- kedro (PyPI): affected all versions; fixed in 1.3.0
- kedro (PyPI): affected all versions; fixed in 1.3.0
- kedro (PyPI): affected all versions; fixed in 1.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35167/ (Markdown: https://insights.sbomify.com/CVE-2026-35167/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35167
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35167
- OSV: https://osv.dev/vulnerability/CVE-2026-35167

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35167/
Summaries are generated and may contain mistakes; the official description above is the record.