Quick answers
- Is CVE-2026-3840 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-3840 being exploited in the wild.
- How severe is CVE-2026-3840?
- High severity, with a CVSS score of 7.1, published 12 June 2026.
- Which products and versions are affected?
- Kedro Kedro 1.2.0.
- Is there a fix for CVE-2026-3840?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-3840 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-3840?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A path traversal vulnerability exists in Kedro 1.2.0 due to insufficient sanitization of user-supplied version strings. The `_get_versioned_path()` method in `kedro/io/core.py` directly interpolates these strings into filesystem paths. An attacker with local access can exploit this via the API or the CLI's `--load-versions` parameter (handled by `_split_load_versions()` in `kedro/framework/cli/utils.py`). By using traversal sequences like '../', an attacker can escape the versioned dataset directory to read or write files elsewhere on the filesystem, potentially leading to data poisoning or cross-tenant data access in automated environments.
Affected products
- Kedro Kedro 1.2.0
Timeline
- 2026-06-12: disclosed
- 2026-06-12: advisory