kedro Known Vulnerabilities & Fixes
kedro has 2 known security vulnerabilities in PyPI (Python). Upgrade to version 1.3.0 or later to resolve all known issues. Data sourced from OSV, enriched with EPSS exploit probability and CISA KEV.
Low Immediate Risk
No actively exploited vulnerabilities detected. Monitor and update in your next maintenance window.
Recommended safe version: 1.3.0
Upgrading to 1.3.0 or later resolves all 2 known vulnerabilities in kedro. Run: pip install "kedro>=1.3.0"
Is kedro in your project?
Check if you're affected and upgrade to 1.3.0 to stay secure.
Security Summary
- 2 affected version ranges have been identified across these 2 advisories.
- 100% of known issues have a published fixed version.
- Remediation: pip install --upgrade kedro
Vulnerabilities
2 unique vulnerabilities — sorted by exploitation risk (KEV → EPSS → CVSS). Click a CVE/GHSA ID for full details. First disclosed Apr 3, 2026, most recently Jun 29, 2026 (87 days apart).
| CVE / GHSA | Severity | Affected | Fixed In |
|---|---|---|---|
| CVE-2024-9701 Kedro deserialization vulnerability | CRITICAL | 0.14.0, 0.14.1, 0.14.2, 0.14.3 (+49 more) | 0.19.9 |
| CVE-2026-35171 Kedro has Arbitrary Code Execution via Malicious Logging Configuration | CRITICAL | 0.14.0, 0.14.1, 0.14.2, 0.14.3 (+63 more) | 1.3.0 |
About This Data
Vulnerability data for kedro is sourced from the Open Source Vulnerability (OSV) database, aggregating reports from GitHub Advisory Database, NIST NVD, and ecosystem-specific sources.
CVSS (Common Vulnerability Scoring System) scores reflect exploitability and impact. EPSS (Exploit Prediction Scoring System) scores indicate the probability of exploitation within the next 30 days. Vulnerabilities marked with are listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.
Related PyPI (Python) Packages
Other packages in this ecosystem, ranked by shared vulnerabilities where available.
Check Your Dependencies
Scan your project to check if you're using a vulnerable version of kedro.