# CVE-2026-111170: kedro-datasets 9.3.0 through 9.6.0 Path Traversal via MatplotlibDataset Plot Name

> Attackers can write or overwrite arbitrary files outside the intended directory by supplying absolute plot names in MatplotlibDataset.save().

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-7vr2-8p3f-2p48

## What is CVE-2026-111170?

CVE-2026-111170 is a high-severity path traversal vulnerability in kedro-org kedro-datasets, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

kedro-datasets from 9.3.0 through 9.6.0 contains a path traversal vulnerability in MatplotlibDataset.save() that allows attackers to write files outside the dataset directory by supplying absolute plot names. Because validate_sub_path() strips leading slashes while pathlib's join discards the base path, attackers can create or overwrite files anywhere the process can write.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

Upgrade to a fixed version.

## Is CVE-2026-111170 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111170 is a high-severity path traversal vulnerability in kedro-org kedro-datasets, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111170 in the wild and no public exploit code.

Affected product: kedro-org kedro-datasets. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111170/ (Markdown: https://insights.sbomify.com/CVE-2026-111170/index.md)
```

## Sources

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

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