Is CVE-2026-35167 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35167 being exploited in the wild.

How severe is CVE-2026-35167?

High severity, with a CVSS score of 7.1, published 6 April 2026.

Which products and versions are affected?

kedro (PyPI) < 1.3.0, ECOSYSTEM:introduced=0,fixed=1.3.0.

Is there a fix for CVE-2026-35167?

Yes. kedro (PyPI): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35167 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-35167?

Check whether you run Linuxfoundation Kedro or kedro (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35167: Kedro path traversal in versioned dataset loading

Q: Which products and versions are affected?

kedro (PyPI) < 1.3.0, ECOSYSTEM:introduced=0,fixed=1.3.0.

Q: Is there a fix for CVE-2026-35167?

Yes. kedro (PyPI): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-35167 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-35167?

Check whether you run Linuxfoundation Kedro or kedro (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35167 · Severity: high · CVSS 7.1 · Published 2026-04-06

Kedro, a data science framework, contains a vulnerability that allows users to access files outside of intended directories. By providing specially crafted version strings, an attacker could read sensitive system files or poison data used in data science pipelines. This could lead to unauthorized data exposure or compromised machine learning models in shared computing environments.

Technologies: kedro (PyPI). Vendors: Linuxfoundation, PyPI.

Quick answers

Is CVE-2026-35167 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35167 being exploited in the wild.
How severe is CVE-2026-35167?: High severity, with a CVSS score of 7.1, published 6 April 2026.
Which products and versions are affected?: kedro (PyPI) < 1.3.0, ECOSYSTEM:introduced=0,fixed=1.3.0.
Is there a fix for CVE-2026-35167?: Yes. kedro (PyPI): upgrade to 1.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35167 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-35167?: Check whether you run Linuxfoundation Kedro or kedro (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

kedro (PyPI): upgrade to 1.3.0 or later
```
pip install "kedro>=1.3.0"
```

Technical details

A path traversal vulnerability exists in the `_get_versioned_path()` method within `kedro/io/core.py`. The component fails to sanitize user-supplied version strings before interpolating them into filesystem paths, allowing the use of `../` sequences. This is exploitable via `catalog.load()`, `DataCatalog.from_config()`, or the CLI using the `--load-versions` flag. An attacker with the ability to influence these inputs can read arbitrary files reachable by the application process or cause the application to load malicious datasets. The issue is resolved in Kedro version 1.3.0 by implementing version string validation.

Affected products

Kedro-org Kedro < 1.3.0

Identifiers

CVE-2026-35167
GHSA-6326-w46w-ppjw
PYSEC-2026-71

Timeline

2026-03-10: patched: Fix merged in pull request 5442
2026-04-01: disclosed
2026-04-03: advisory: GitHub Advisory published
2026-04-06: other: NVD published date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.