Kurz gesagt
- CVE-2026-35171 ist eine Schwachstelle (KRITISCH (CVSS 9.8)) in kedro, kedro (linuxfoundation).
- Wahrscheinlichkeit einer Ausnutzung in den nächsten 30 Tagen (EPSS): 0.71%, höher als bei 53.7% aller Schwachstellen.
- Abhilfe: auf 1.3.0 oder neuer aktualisieren.
| Package | Affected versions | Patched versions |
|---|
| kedro PyPI | < 1.3.0
| 1.3.0
|
| kedro | < 1.3.0
| 1.3.0
|
Description
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:
- Do not allow untrusted input to control the
KEDRO_LOGGING_CONFIG 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.
References
NVD 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.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free