INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2026-35171

Kedro has Arbitrary Code Execution via Malicious Logging Configuration

CVE-2026-35171 · 2026-04-03 critical

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Code and command execution
Affected
kedro (PyPI)
CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% chance of exploitation in 30 days

How it works, in short

Setting the logging config path to a file containing a special factory key makes dictConfig call an arbitrary callable at application startup. (Our summary, written by a model. The source text is below.)

Details

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

- Kedro 1.3.0

Users should upgrade to this version as soon as possible.

---

Workarounds

If upgrading is not immediately possible:

These mitigations reduce risk but do not fully eliminate it.

---

References

References

Source: GitHub Advisory Database, used under CC BY 4.0.