CVE-2026-35171: Kedro Kedro Has Arbitrary Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-9cqf-439c-j96r
Share
CVSS 9.8
CWE-502 CWE-94
Published
Advisory Summary

CVE-2026-35171 is a CRITICAL (CVSS 9.8) kedro has arbitrary code execution vulnerability (CWE-502: Deserialization of Untrusted Data) affecting Kedro libraries in the PyPI ecosystem. The issue involves kedro has arbitrary code execution via malicious logging configuration. Remediation is available by upgrading affected packages to version 1.3.0.

CVE-2026-35171 at a Glance

CVE Identifier CVE-2026-35171
GHSA Identifier GHSA-9cqf-439c-j96r
Severity CRITICAL
CVSS v3.1 Base Score 9.8
CWE Classification CWE-502: Deserialization of Untrusted Data
Affected Product Kedro
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 9.8

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-35171

To remediate this vulnerability, upgrade all affected Kedro dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

kedro fixed: 1.3.0 
pip install kedro>=1.3.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show kedro

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-35171, inspect your installed packages using pip:

pip show kedro

Analyze the terminal output to locate any version of Kedro in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.3.0), your application is affected.

Note: The pip show kedro command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-502: Deserialization of Untrusted Data, where the product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. In Kedro, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-35171 Affected Kedro Versions

1 component(s)
Fixed Versions:
1.3.0
Product / Package Ecosystem Affected Versions Fixed Version
kedro
pypi/kedro
PyPI
< 1.3.0
1.3.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/kedro-org/kedro/security/advisories/GHSA-9cqf-439c-j96r
NVD — CVE-2026-35171 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-35171
Kedro Source Repository REPOSITORY
https://github.com/kedro-org/kedro
Kedro Source Repository REPOSITORY
https://github.com/pypa/advisory-database/tree/main/vulns/kedro/PYSEC-2026-72.yaml

Frequently Asked Questions

What is CVE-2026-35171?
CVE-2026-35171 is a security vulnerability in Kedro involving Kedro has Arbitrary Code Execution via Malicious Logging Configuration under CWE-502: Deserialization of Untrusted Data.
Which Kedro versions are affected?
Affected versions include releases prior to 1.3.0 across affected packages: kedro.
What version fixes CVE-2026-35171?
Upgrading to 1.3.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is kedro affected?
Yes, kedro is affected in releases prior to 1.3.0. Upgrade your dependency to 1.3.0 or later.
What is the CVSS score of CVE-2026-35171?
CVE-2026-35171 has a CVSS v3.1 base score of 9.8 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2026-35171?
CVE-2026-35171 is classified under CWE-502: Deserialization of Untrusted Data (The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.).
How can I check PyPI dependencies for CVE-2026-35171?
Run the dependency tree command: 'pip show kedro'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9cqf-439c-j96r",
  "modified" : "2026-06-06T00:23:45Z",
  "published" : "2026-04-03T03:48:48Z",
  "aliases" : [ "CVE-2026-35171" ],
  "summary" : "Kedro has Arbitrary Code Execution via Malicious Logging Configuration",
  "details" : "### Impact\n\nThis is a **critical remote code execution (RCE)** vulnerability caused by unsafe use of `logging.config.dictConfig()` with user-controlled input.\n\nKedro 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.\n\n---\n\n### Patches\n\nThe vulnerability is fixed by introducing validation that rejects the unsafe `()` factory key in logging configurations before passing them to `dictConfig()`.\n\n#### Fixed in\n- Kedro 1.3.0\n\nUsers should upgrade to this version as soon as possible.\n\n---\n\n### Workarounds\n\nIf upgrading is not immediately possible:\n\n- Do not allow untrusted input to control the `KEDRO_LOGGING_CONFIG` environment variable  \n- Restrict write access to logging configuration files  \n- Avoid using externally supplied or dynamically generated logging configs  \n- Manually validate logging YAML to ensure it does not contain the `()` key  \n\nThese mitigations reduce risk but do not fully eliminate it.\n\n---\n\n### References\n\n- Python logging configuration documentation: https://docs.python.org/3/library/logging.config.html#logging-config-dictschema  \n- CWE-94: Code Injection — https://cwe.mitre.org/data/definitions/94.html",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "kedro"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.3.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/kedro-org/kedro/security/advisories/GHSA-9cqf-439c-j96r"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-35171"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/kedro-org/kedro"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/pypa/advisory-database/tree/main/vulns/kedro/PYSEC-2026-72.yaml"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-502", "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-03T03:48:48Z",
    "nvd_published_at" : "2026-04-06T18:16:43Z"
  }
}