CVE-2026-35171: Arbitrary Code Execution via Malicious Logging Configuration in Kedro
Impact
This is a critical Remote Code Execution (RCE) vulnerability caused by unsafe use of logging.config.dictConfig() with user-controlled input.
Kedro allows the logging configuration file path to be set via the KEDROLOGGINGCONFIG 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.
---
Patches
The vulnerability is fixed by introducing validation that rejects the unsafe () factory key in logging configurations before passing them to dictConfig().
Fixed in - Kedro 1.3.0
Users should upgrade to this version as soon as possible.
---
Workarounds
If upgrading is not immediately possible:
- Do not allow untrusted input to control the KEDROLOGGINGCONFIG environment variable - Restrict write access to logging configuration files - Avoid using externally supplied or dynamically generated logging configs - Manually validate logging YAML to ensure it does not contain the () key
These mitigations reduce risk but do not fully eliminate it.
Other sources
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 KEDROLOGGINGCONFIG 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.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
pip/kedroto a version that resolves this vulnerability.Fixed in 1.3.0 - Upgrade
Upgrade
Kedroto a version that resolves this vulnerability.Fixed in 1.3.0 - Configuration
Ensure the KEDRO_LOGGING_CONFIG environment variable is not set or influenced by untrusted users/processes; do not allow untrusted input to control it.
Kedro KEDRO_LOGGING_CONFIG = Do not allow untrusted input to control this environment variable - Configuration
If upgrading is not immediately possible, manually validate the logging YAML to ensure it does not contain the `()` key.
Logging configuration Logging YAML key `()` = Must be absent - Compensating control
Restrict write access to logging configuration files so attackers cannot modify them.