{"answers":{"affected":"3 open source packages ship an affected version, including kedro. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35167 in the wild and no public exploit code.","fix":"Upgrade kedro to 1.3.0 or later.","what":"CVE-2026-35167 is a high-severity path traversal vulnerability in kedro-org kedro, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35167 and fix it if it is affected.\n\nWhat it is: CVE-2026-35167 is a high-severity path traversal vulnerability in kedro-org kedro, published on 6 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35167 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kedro (PyPI): affected all versions; fixed in 1.3.0\n- kedro (PyPI): affected all versions; fixed in 1.3.0\n- kedro (PyPI): affected all versions; fixed in 1.3.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-35167/ (Markdown: https://insights.sbomify.com/CVE-2026-35167/index.md)","id":"CVE-2026-35167","markdown":"https://insights.sbomify.com/CVE-2026-35167/index.md","name":"CVE-2026-35167","record":{"aliases":["GHSA-6326-w46w-ppjw","PYSEC-2026-71"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Kedro data science library","requires_auth":"low_privilege","summary":"Attackers can manipulate version strings to read or modify files outside the intended dataset directory in Kedro data science projects.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kedro","vendor":"linuxfoundation"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.\nThis 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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kedro has a path traversal in versioned dataset loading via unsanitized version string","id":"CVE-2026-35167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"OpenSTAManager: SQL Injection via Aggiornamenti Module","id":"CVE-2026-35168"},"packages":[{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":null,"source":"GHSA-6326-w46w-ppjw"},{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":"pkg:pypi/kedro","source":"GHSA-6326-w46w-ppjw"},{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":"pkg:pypi/kedro","source":"PYSEC-2026-71"}],"prev":{"headline":"Hugo does not properly escape some Markdown links","id":"CVE-2026-35166"},"products":["kedro"],"published":"2026-04-06","related":[{"cvss_score":9.8,"headline":"Arbitrary Code Execution via Malicious Logging Configuration in Kedro","id":"CVE-2026-35171","kev_date_added":null,"published":"2026-04-06"},{"cvss_score":7.1,"headline":"Path Traversal in kedro-org/kedro","id":"CVE-2026-3840","kev_date_added":null,"published":"2026-06-12"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["kedro-org"]},"summary":"Attackers can manipulate version strings to read or modify files outside the intended dataset directory in Kedro data science projects.","url":"https://insights.sbomify.com/CVE-2026-35167/"}