{"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-35171 in the wild and no public exploit code.","fix":"Upgrade kedro to 1.3.0 or later.","what":"CVE-2026-35171 is a critical code injection vulnerability in kedro-org kedro, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35171 and fix it if it is affected.\n\nWhat it is: CVE-2026-35171 is a critical code injection vulnerability in kedro-org kedro, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35171 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-35171/ (Markdown: https://insights.sbomify.com/CVE-2026-35171/index.md)","id":"CVE-2026-35171","markdown":"https://insights.sbomify.com/CVE-2026-35171/index.md","name":"CVE-2026-35171","record":{"aliases":["GHSA-9cqf-439c-j96r","PYSEC-2026-72"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kedro data science library","requires_auth":"none","summary":"Attackers can execute arbitrary code by manipulating the logging configuration path via an environment variable in Kedro.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"kedro","vendor":"linuxfoundation"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"Kedro is a toolbox for production-ready data science. Prior to 1.3.0, Kedro allows the logging configuration file path to be set via the KEDRO_LOGGING_CONFIG environment variable and loads it without validation. The logging configuration schema supports the special () key, which enables arbitrary callable instantiation. An attacker can exploit this to execute arbitrary system commands during application startup. This is a critical remote code execution (RCE) vulnerability caused by unsafe use of logging.config.dictConfig() with user-controlled input. 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":"Arbitrary Code Execution via Malicious Logging Configuration in Kedro","id":"CVE-2026-35171","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Distribution has stale blob access resurrection via repo-scoped redis descriptor cache invalidation","id":"CVE-2026-35172"},"packages":[{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":null,"source":"GHSA-9cqf-439c-j96r"},{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":"pkg:pypi/kedro","source":"GHSA-9cqf-439c-j96r"},{"ecosystem":"PyPI","fixed":["1.3.0"],"introduced":["0"],"last_affected":[],"package":"kedro","purl":"pkg:pypi/kedro","source":"PYSEC-2026-72"}],"prev":{"headline":"openFPGALoader has a heap buffer overflow in BitParser::parseHeader() via crafted .bit file","id":"CVE-2026-35170"},"products":["kedro"],"published":"2026-04-06","related":[{"cvss_score":7.1,"headline":"Path Traversal in kedro-org/kedro","id":"CVE-2026-3840","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":7.1,"headline":"Kedro has a path traversal in versioned dataset loading via unsanitized version string","id":"CVE-2026-35167","kev_date_added":null,"published":"2026-04-06"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["kedro-org"]},"summary":"Attackers can execute arbitrary code by manipulating the logging configuration path via an environment variable in Kedro.","url":"https://insights.sbomify.com/CVE-2026-35171/"}