[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"repo-stars":3,"vuln-CVE-2026-35171":6},{"stargazers_count":4,"fetched_at":5},5,"2026-04-06T21:11:21.470Z",{"id":7,"descriptions":8,"cisa":9,"weaknesses":10,"exploits":41,"aliases":42,"duplicate_of":9,"upstream":44,"downstream":45,"duplicates":46,"related":47,"reserved_at":9,"published_at":48,"modified_at":48,"state":49,"summary":50,"references_raw":57,"kevs":71,"epss":9,"epss_history":72,"metrics":73,"affected":82},"CVE-2026-35171","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.",null,[11,32],{"_key":12,"id":12,"name":13,"description":14,"type":15,"status":16,"abstraction":17,"likelihood_of_exploit":18,"capec":19},"CWE-94","Improper Control of Generation of Code ('Code Injection')","The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.","weakness","Draft","Base","Medium",[20,24,28],{"id":21,"name":22,"techniques":23},"CAPEC-242","Code Injection",[],{"id":25,"name":26,"techniques":27},"CAPEC-35","Leverage Executable Code in Non-Executable Files",[],{"id":29,"name":30,"techniques":31},"CAPEC-77","Manipulating User-Controlled Variables",[],{"_key":33,"id":33,"name":34,"description":35,"type":15,"status":16,"abstraction":17,"likelihood_of_exploit":18,"capec":36},"CWE-502","Deserialization of Untrusted Data","The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.",[37],{"id":38,"name":39,"techniques":40},"CAPEC-586","Object Injection",[],[],[43],"GHSA-9cqf-439c-j96r",[],[],[],[],"2026-04-06T17:45:45.664Z","Received",{"cisa_kev":51,"cisa_ransomware":51,"cisa_vendor":9,"epss_severity":9,"epss_score":9,"severity":52,"severity_score":53,"severity_version":54,"severity_source":55,"severity_vector":56,"severity_status":49},false,"critical",9.8,"v3.1","cve.org","CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",[58,66],{"url":59,"sources":60,"tags":63},"https://github.com/kedro-org/kedro/security/advisories/GHSA-9cqf-439c-j96r",[61,55,62],"osv_pypi","nvd",[64,65],"WEB","X Refsource CONFIRM",{"url":67,"sources":68,"tags":69},"https://github.com/kedro-org/kedro",[61],[70],"PACKAGE",[],[],[74,77,80],{"source":61,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":75,"cvss_v4_0":9},{"baseScore":53,"baseSeverity":9,"vectorString":56,"impactScore":53,"exploitabilityScore":76},10,{"source":55,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":78,"cvss_v4_0":9},{"baseScore":53,"baseSeverity":79,"vectorString":56,"impactScore":53,"exploitabilityScore":76},"CRITICAL",{"source":62,"cvss_v2_0":9,"cvss_v3_0":9,"cvss_v3_1":81,"cvss_v4_0":9},{"baseScore":53,"baseSeverity":79,"vectorString":56,"impactScore":53,"exploitabilityScore":76},[83,93],{"ecosystem":9,"name":84,"vendor":85,"product":84,"cpe_part":86,"purl_type":9,"purl_namespace":9,"purl_name":9,"source":9,"versions":87},"kedro","kedro-org","a",[88],{"version":89,"is_range":90,"range_type":55,"version_start":9,"version_start_type":9,"version_end":91,"version_end_type":92,"fixed_in":9},"\u003C 1.3.0",true,"1.3.0","excluding",{"ecosystem":94,"name":84,"vendor":94,"product":84,"cpe_part":9,"purl_type":95,"purl_namespace":9,"purl_name":84,"source":9,"versions":96},"PyPI","pypi",[97],{"version":98,"is_range":90,"range_type":99,"version_start":9,"version_start_type":9,"version_end":91,"version_end_type":92,"fixed_in":9},"lt1_3_0","ecosystem"]