kedro (pypi) has 4 known vulnerabilities, the worst rated CRITICAL. No single fixed version is recorded that clears every advisory, so check each one below. No malicious-package signal is recorded.
59 direct dependencies
16 carry known advisories, worst CRITICAL
No published models are known to use this package.
CVSS v3.1 base score out of 10
chance of exploitation in 30 days, 55th percentile of all CVEs
CyberXYZ composite out of 10
fig. 01 — GHSA-9cqf-439c-j96r, the advisory selected below
This is a critical remote code execution (RCE) vulnerability caused by unsafe use of logging.config.dictConfig() with user-controlled input.
Full advisory text at GitHub advisory or NVD.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CyberXYZ does not call a package safe in absolute terms. It records 4 known vulnerabilities for kedro (pypi), the worst rated CRITICAL, and no malicious-package signal. Whether it is acceptable depends on the version you run.
Yes. CyberXYZ records 4 known vulnerabilities for kedro (pypi), the worst rated CRITICAL. They are GHSA-9cqf-439c-j96r, GHSA-747f-ww56-4q4h, GHSA-6326-w46w-ppjw, GHSA-rm69-wvpv-r2w7.
Search kedro in CyberXYZ Check at https://cyberxyz.io/check?q=kedro. The xyz Scanner checks a project's dependencies, and CyberXYZ Proxy checks each package as it is installed.
Checked 2026-11-14 at 12:04 UTC. The most recent advisory here was published 2026-04-03. Updated continuously from NVD, GHSA, OSV and CNA feeds.