CVE-2026-35171

Arbitrary Code Execution via Malicious Logging Configuration in Kedro

Published Apr 6, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Kedro, a production‑ready data science toolkit, previously allowed a logging configuration file path to be set through the KEDRO_LOGGING_CONFIG environment variable. The logging configuration schema accepts a special () key that can instantiate arbitrary callables, enabling an attacker to execute system commands when the application starts. This flaw permits attackers to inject malicious code and run arbitrary commands with the same privileges as the Kedro process, compromising confidentiality, integrity, and availability of the system.

Affected Systems

The vulnerability affects the Kedro project provided by the Linux Foundation (kedro-org:kedro). All releases prior to version 1.3.0 are impacted, as the unsafe handling of user‑controlled logging configuration exists only in those older builds.

Risk and Exploitability

The CVSS score of 9.8 signals a critical severity, while an EPSS score below 1% indicates that exploit attempts are currently rare or not well known. The feature is not listed in the CISA KEV catalog. Exploitation requires an attacker to influence the KEDRO_LOGGING_CONFIG environment variable or supply a malicious logging configuration file that the Kedro process loads during startup. Once the environment variable is set to a file containing a dangerous callable, the attacker can run arbitrary code in the context of the Kedro application.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Kedro to version 1.3.0 or later.

Generated by OpenCVE AI on April 14, 2026 at 16:33 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-9cqf-439c-j96r Kedro has Arbitrary Code Execution via Malicious Logging Configuration
History
Type Values Removed Values Added
First Time appeared Linuxfoundation
Linuxfoundation kedro
CPEs cpe:2.3:a:linuxfoundation:kedro:*:*:*:*:*:python:*:*
Vendors & Products Linuxfoundation
Linuxfoundation kedro
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Kedro-org
Kedro-org kedro
Vendors & Products Kedro-org
Kedro-org kedro
Type Values Removed Values Added
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.
Title Arbitrary Code Execution via Malicious Logging Configuration in Kedro
Weaknesses CWE-502
CWE-94
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-502

    Deserialization of Untrusted Data

  • CWE-94

    Improper Control of Generation of Code ('Code Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 7, 2026, 3:10 PM
Reserved
Apr 1, 2026, 5:26 PM
Status
Analyzed
Published
Apr 6, 2026, 6:16 PM
Modified
Jul 24, 2026, 9:10 PM