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

> Attackers can execute arbitrary code by manipulating the logging configuration path via an environment variable in Kedro.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-9cqf-439c-j96r, PYSEC-2026-72

## What is CVE-2026-35171?

CVE-2026-35171 is a critical code injection vulnerability in kedro-org kedro, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-35171?

3 open source packages ship an affected version, including kedro. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kedro` | PyPI | All versions | 1.3.0 |
| `kedro` | PyPI | All versions | 1.3.0 |
| `kedro` | PyPI | All versions | 1.3.0 |

Products: Linuxfoundation Kedro.

## How do I fix CVE-2026-35171?

Upgrade kedro to 1.3.0 or later.

## Is CVE-2026-35171 being exploited?

There is no known exploitation of CVE-2026-35171 in the wild and no public exploit code.

## Other vulnerabilities in kedro-org kedro

- [CVE-2026-3840](https://insights.sbomify.com/CVE-2026-3840/): Path Traversal in kedro-org/kedro (high 7.1)
- [CVE-2026-35167](https://insights.sbomify.com/CVE-2026-35167/): Kedro has a path traversal in versioned dataset loading via unsanitized version string (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35171 and fix it if it is affected.

What it is: CVE-2026-35171 is a critical code injection vulnerability in kedro-org kedro, published on 6 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35171 in the wild and no public exploit code.

Affected packages and fixed versions:
- kedro (PyPI): affected all versions; fixed in 1.3.0
- kedro (PyPI): affected all versions; fixed in 1.3.0
- kedro (PyPI): affected all versions; fixed in 1.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35171/ (Markdown: https://insights.sbomify.com/CVE-2026-35171/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35171
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35171
- OSV: https://osv.dev/vulnerability/CVE-2026-35171

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35171/
Summaries are generated and may contain mistakes; the official description above is the record.