
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-35492 is a path traversal vulnerability (CWE-22) in the PartitionedDataset component of the kedro-datasets Python package that allows authenticated attackers to write files to arbitrary locations on the filesystem. All versions of kedro-datasets prior to 9.3.0 are affected, regardless of storage backend (local filesystem, S3, GCS, etc.). The vulnerability was reported by security researcher "redyank" on March 16, 2026, patched on March 18, 2026, and publicly disclosed via GitHub Security Advisory on April 3, 2026. It carries a CVSS v3.1 base score of 6.5 (Medium) (GitHub Advisory, Kedro Advisory).
The root cause is insufficient input validation in PartitionedDataset: partition IDs supplied by users or external input were concatenated directly with the dataset's configured base path without normalization or boundary checks (CWE-22). An attacker can craft a partition ID containing .. path traversal components (e.g., ../../etc/cron.d/malicious), causing the resulting file path to resolve outside the intended dataset directory. The fix, introduced in PR #1346, applies posixpath.normpath to the constructed path and verifies it remains within the base directory before use, raising a DatasetError if the check fails. posixpath was chosen specifically because PartitionedDataset uses fsspec for multi-backend support, requiring consistent POSIX-style path handling across local, S3, and GCS backends (GitHub Advisory, Fix PR).
Successful exploitation allows an authenticated, low-privileged attacker to write files to arbitrary locations on the filesystem, potentially overwriting critical system files, configuration files, or application code. This can escalate to remote code execution if an attacker overwrites executable scripts, cron jobs, or web-accessible files. Confidentiality and availability are not directly impacted by the vulnerability itself, but integrity is rated High; the attack surface extends to any storage backend supported by fsspec, including cloud object stores like S3 and GCS (GitHub Advisory, Kedro Advisory).
There is no confirmed in-the-wild exploitation of this vulnerability. A GitHub repository (https://github.com/redyank/CVE-2026-35492) was flagged as a potential PoC, but analysis determined it contains only a README with vulnerability description and patch information — no runnable exploit code or reproduction steps are present. The EPSS score is approximately 0.014–0.018%, indicating a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (GitHub Advisory, Feedly).
kedro-datasets < 9.3.0 that uses PartitionedDataset and accepts externally-supplied partition IDs (e.g., via a data pipeline API or user-controlled input)... traversal sequences, such as ../../etc/cron.d/backdoor or ../../home/user/.ssh/authorized_keys, targeting a writable file outside the dataset directory.PartitionedDataset processes it. The partition ID is concatenated with the base path without validation, resulting in a resolved path outside the configured dataset directory.PartitionedDataset base directory; modifications to sensitive files (e.g., /etc/cron.d/, ~/.ssh/authorized_keys, web root directories) with timestamps correlating to pipeline execution times.DatasetError exceptions referencing path traversal (post-patch); pipeline execution logs with partition IDs containing .. sequences.The vulnerability is patched in kedro-datasets version 9.3.0; users should upgrade immediately using pip install 'kedro-datasets>=9.3.0'. For users unable to upgrade, the recommended workaround is to validate all partition IDs before passing them to PartitionedDataset, explicitly rejecting any IDs containing .. path components. The fix is available in commit 65115f7 and the release is tagged at kedro-datasets-9.3.0 (GitHub Advisory, Fix PR).
The vulnerability was discovered and responsibly disclosed by community researcher "redyank", who followed Kedro's security policy by filing a placeholder issue and sending a detailed report with proof of concept to maintainers via email. The Kedro maintainers responded promptly, merging the fix within two days of the report and coordinating CVE assignment and GHSA publication. Redyank was credited as the reporter in the official advisory, and the maintainers were praised for their quick response and coordinated disclosure approach (Fix PR, Kedro Advisory).
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."