| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9cqf-439c-j96r | Kedro has Arbitrary Code Execution via Malicious Logging Configuration |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 07 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 07 Apr 2026 09:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kedro-org
Kedro-org kedro |
|
| Vendors & Products |
Kedro-org
Kedro-org kedro |
Mon, 06 Apr 2026 18:00:00 +0000
| 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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-07T15:10:37.613Z
Reserved: 2026-04-01T17:26:21.133Z
Link: CVE-2026-35171
Updated: 2026-04-07T15:07:55.111Z
Status : Undergoing Analysis
Published: 2026-04-06T18:16:43.373
Modified: 2026-04-07T13:20:11.643
Link: CVE-2026-35171
No data.
OpenCVE Enrichment
Updated: 2026-04-07T09:37:57Z
Github GHSA