Categories
CVE-2026-35492

Path Traversal in kedro-datasets (CVE-2026-35492)

Summary

Path traversal in kedro-datasets (CVE-2026-35492). Data can be tampered with by attackers. Exploitable via posixpath.normpath. Mitigation: upgrade to 9.3.0 or later.

Original description

The description as published by the source.

Impact

PartitionedDataset in kedro-datasets was vulnerable to path traversal. Partition IDs were concatenated directly with the dataset base path without validation. An attacker or malicious input containing .. components in a partition ID could cause files to be written outside the configured dataset directory, potentially overwriting arbitrary files on the filesystem.
Users of PartitionedDataset with any storage backend (local filesystem, S3, GCS, etc.) are affected.

Patches

Yes. The vulnerability has been patched in kedro-datasets version 9.3.0.
Users should upgrade to kedro-datasets >= 9.3.0. The fix normalizes constructed paths using posixpath.normpath and validates that the resolved path remains within the dataset base directory before use, raising a DatasetError if the path escapes the base directory.

Workarounds

Users who cannot upgrade should validate partition IDs before passing them to PartitionedDataset, ensuring they do not contain .. path components.

References

Fix: https://github.com/kedro-org/kedro-plugins/pull/1346
Report: https://github.com/kedro-org/kedro/issues/5452

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-35492 has been found in kedro-datasets.
Attackers can target a specific entry point like posixpath.normpath over the network to misuse the product.
Data can be tampered with by attackers.
What to do: upgrade kedro-datasets to 9.3.0 or later.
If unsure, ask your IT team or search "kedro-datasets CVE-2026-35492" on the vendor's site.

CVE-2026-35492 (kedro-datasets) — CWE-22
Attack vector: remote (network-reachable) / no user interaction
Attack surface: posixpath.normpath / DatasetError
Patched: 9.3.0 — apply immediately
Workaround: Users who cannot upgrade should validate partition IDs before passing them to PartitionedDataset, ensuring they do not contain .. path components.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in kedro-datasets. Attackers reach the vulnerable code path via posixpath.normpath.

📍 Affected scope

Check the vendor advisory for the affected versions of kedro-datasets. Attack surface: posixpath.normpath / DatasetError.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 9.3.0.

🛡️ Workaround

Workaround: Users who cannot upgrade should validate partition IDs before passing them to PartitionedDataset, ensuring they do not contain .. path components.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'kedro-datasets' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'kedro-datasets' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で kedro-datasets を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate
    Users who cannot upgrade should validate partition IDs before passing them to PartitionedDataset, ensuring they do not contain `..` path components.

    パッチが適用されるまでの応急処置として、Users who cannot upgrade should validate partition IDs before passing them to PartitionedDataset, ensuring they do not contain .. path components. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch
    Upgrade kedro-datasets to 9.3.0

    ステージング環境で 9.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI kedro-datasets
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"9.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details