kedro
Affected
- introduced
0, fixed1.3.0(ecosystem)
Fixed versions
1.3.0
Fix
- Fixed version
1.3.0pip install --upgrade kedro==1.3.0
Advisory
Also known as: CVE-2026-35171, PYSEC-2026-72
Kedro has Arbitrary Code Execution via Malicious Logging Configuration
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 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.
---
Patches
The vulnerability is fixed by introducing validation that rejects the unsafe () factory key in logging configurations before passing them to dictConfig().
Fixed in
Users should upgrade to this version as soon as possible.
---
Workarounds
If upgrading is not immediately possible:
KEDRO_LOGGING_CONFIG environment variable () key These mitigations reduce risk but do not fully eliminate it.
---
References
Critical Basis: The source's own band: CRITICAL
0, fixed 1.3.0 (ecosystem)1.3.0
1.3.0pip install --upgrade kedro==1.3.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0