---
title: "CVE-2026-35171: Kedro has Arbitrary Code Execution via Malicious Logging Configuration"
url: https://erroneo.us/security/cve/CVE-2026-35171/
description: "CVE-2026-35171 (kedro (PyPI)): Kedro is a toolbox for production-ready data science. Prior to 1.3.0, Kedro allows the logging configuration file path to be…"
type: vulnerability-record
section: "Security Digest"
date_published: 2026-04-06
date_modified: 2026-06-06
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2026-35171"
kev: false
cvss: 9.8
epss: 0.00878
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2026-35171: Kedro has Arbitrary Code Execution via Malicious Logging Configuration

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
- EPSS 0.9% , percentile 59: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 59% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes kedro (PyPI) < 1.3.0, fixed in 1.3.0 . Check your lockfile, including transitive dependencies.

## What it is

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

## Affected packages

- PyPI `kedro` < 1.3.0 → fixed: 1.3.0

## Affected products (CVE record)

- kedro-org kedro: < 1.3.0

## Severity

- GitHub_M CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`
- GitHub CVSS 3.1: 9.8 `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation none , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.88% probability of exploitation activity in the next 30 days; percentile 59.

## Sources

- [GitHub Advisory GHSA-9cqf-439c-j96r](https://github.com/advisories/GHSA-9cqf-439c-j96r)
- [CVE.org record CVE-2026-35171](https://www.cve.org/CVERecord?id=CVE-2026-35171)
- [NVD entry CVE-2026-35171](https://nvd.nist.gov/vuln/detail/CVE-2026-35171)
- [github.com](https://github.com/kedro-org/kedro/security/advisories/GHSA-9cqf-439c-j96r)
- [github.com](https://github.com/pypa/advisory-database/tree/main/vulns/kedro/PYSEC-2026-72.yaml)

---
Source page: https://erroneo.us/security/cve/CVE-2026-35171/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt