Kedro: Path Traversal in versioned dataset loading via unsanitized version string

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-35167: 0.33% estimated exploitation activity in the next 30 days; percentile 26.56 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact The getversionedpath() 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.fromconfig(..., loadversions=...), 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. Patches Yes. Fixed in kedro version 1.3.0. Users should upgrade to kedro = 1.3.0. Workarounds Validate version strings before passing them to DataCatalog or the CLI, ensuring they do not contain .. segments, path separators, or absolute paths.

Published by the source

3 Apr 2026, 03:46 UTC

Last modified by the source

6 Jun 2026, 00:30 UTC

Source last checked

26 Oct 2026, 13:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6326-w46w-ppjw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6326-w46w-ppjw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35167

Advisory: Kedro: Path Traversal in versioned dataset loading via unsanitized version string
IDs: CVE-2026-35167, GHSA-6326-w46w-ppjw
Record: https://patchnext.com/advisories/cve-2026-35167 (revision 2, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: kedro 1.3.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI kedro: affected < 1.3.0; fixed in 1.3.0

## Suggested inspection (read-only)
- `python -m pip show kedro`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on kedro.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-6326-w46w-ppjw (OSV record GHSA-6326-w46w-ppjw lists affected ranges: PyPI kedro >=0 <1.3.0 (fixed))
- Verified: https://github.com/advisories/GHSA-6326-w46w-ppjw (GitHub-reviewed advisory GHSA-6326-w46w-ppjw lists affected ranges: PyPI kedro >=0 <1.3.0)

Commands are suggestions: review each one before running it.