CVE-2026-35171

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 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

• Python logging configuration documentation: https://docs.python.org/3/library/logging.config.html#logging-config-dictschema
• CWE-94: Code Injection, https://cwe.mitre.org/data/definitions/94.html

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.

Untrusted input is evaluated as executable code within the application's runtime environment. Typical impact: arbitrary code execution within the application's privilege context.

CVE-2026-35171 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.0); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability is fixed by introducing validation that rejects the unsafe () factory key in logging configurations before passing them to dictConfig().

1. What is CVE-2026-35171? CVE-2026-35171 is a critical-severity code injection vulnerability in kedro (pip), affecting versions < 1.3.0. It is fixed in 1.3.0. Untrusted input is evaluated as executable code within the application's runtime environment.
2. How severe is CVE-2026-35171? CVE-2026-35171 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of kedro are affected by CVE-2026-35171? kedro (pip) versions < 1.3.0 is affected.
4. Is there a fix for CVE-2026-35171? Yes. CVE-2026-35171 is fixed in 1.3.0. Upgrade to this version or later.
5. Is CVE-2026-35171 exploitable, and should I be worried? Whether CVE-2026-35171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-35171 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-35171? Upgrade kedro to 1.3.0 or later.

Other vulnerabilities in kedro