{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-62997 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-62997 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-62997 is a high-severity unsafe deserialization vulnerability in kedro-org kedro-plugins, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-62997 and fix it if it is affected.\n\nWhat it is: CVE-2026-62997 is a high-severity unsafe deserialization vulnerability in kedro-org kedro-plugins, published on 16 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-62997 in the wild and no public exploit code.\n\nAffected product: kedro-org kedro-plugins. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-62997/ (Markdown: https://insights.sbomify.com/CVE-2026-62997/index.md)","id":"CVE-2026-62997","markdown":"https://insights.sbomify.com/CVE-2026-62997/index.md","name":"CVE-2026-62997","record":{"aliases":["GHSA-f9q4-h45w-jrrq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Kedro data connector","requires_auth":"none","summary":"Attackers can execute arbitrary code via malicious PyTorch model files in the experimental Kedro-Datasets component if users load untrusted data.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Kedro-Datasets provides data connectors for Kedro. From version 5.0.0 until 9.5.0, kedro_datasets_experimental.pytorch.PyTorchDataset in kedro-datasets loads .pt model files with torch.load without enforcing weights_only=True, and user-supplied load_args are silently dropped. On PyTorch versions earlier than 2.6, a malicious pickle-backed model from an attacker-influenced shared registry, downloaded checkpoint, or partitioned external source can execute arbitrary code when a Kedro pipeline loads it. The issue affects only the opt-in kedro_datasets_experimental component and does not affect users who load only trusted files. This issue is fixed in version 9.5.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Kedro-Datasets: Remote code execution in experimental `PyTorchDataset` via unsafe `torch.load`","id":"CVE-2026-62997","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"REDAXO: Unwhitelisted ORDER BY Column in rex_list Allows Authenticated Column Enumeration","id":"CVE-2026-62998"},"packages":[],"prev":{"headline":"Smarty Security stream restriction bypass through stream: resource","id":"CVE-2026-62996"},"products":["kedro-plugins"],"published":"2026-09-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["kedro-org"]},"summary":"Attackers can execute arbitrary code via malicious PyTorch model files in the experimental Kedro-Datasets component if users load untrusted data.","url":"https://insights.sbomify.com/CVE-2026-62997/"}