Kedro, a production‑ready data science toolkit, previously allowed a logging configuration file path to be set through the KEDRO_LOGGING_CONFIG environment variable. The logging configuration schema accepts a special () key that can instantiate arbitrary callables, enabling an attacker to execute system commands when the application starts. This flaw permits attackers to inject malicious code and run arbitrary commands with the same privileges as the Kedro process, compromising confidentiality, integrity, and availability of the system.

The vulnerability affects the Kedro project provided by the Linux Foundation (kedro-org:kedro). All releases prior to version 1.3.0 are impacted, as the unsafe handling of user‑controlled logging configuration exists only in those older builds.

The CVSS score of 9.8 signals a critical severity, while an EPSS score below 1% indicates that exploit attempts are currently rare or not well known. The feature is not listed in the CISA KEV catalog. Exploitation requires an attacker to influence the KEDRO_LOGGING_CONFIG environment variable or supply a malicious logging configuration file that the Kedro process loads during startup. Once the environment variable is set to a file containing a dangerous callable, the attacker can run arbitrary code in the context of the Kedro application.