CVE-2026-35167HIGH 8.1EPSS p24.3%

CVE-2026-35167CVE-2026-35167

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.

Scoring

CVSS 3.18.1 (HIGH)
VectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS0.33% probability of exploitation · percentile 24.3% · 2026-06-19T12:03:05Z
Published2026-04-06
Last modified2026-04-14

Underlying weaknesses· 1

CWE-22

References

  1. https://github.com/kedro-org/kedro/pull/5442
  2. https://github.com/kedro-org/kedro/security/advisories/GHSA-6326-w46w-ppjw

1

TypeTargetConfidenceTier
WeaknessImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal')cwe-220%live

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CVE
CVE-2026-35171
CVE
CVE-2025-12638
CVE
CVE-2026-5422
CVE
CVE-2026-35397
CVE
CVE-2026-1462
CVE
CVE-2026-38428
Sourced from NVD + FIRST.org EPSS. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.