# CVE-2026-5258: Sanster IOPaint File Manager file_manager.py _get_file path traversal

> Remote attackers can exploit a path traversal flaw in the IOPaint file manager to read arbitrary files from the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-qw2j-qjh4-32jw

## What is CVE-2026-5258?

CVE-2026-5258 is a medium-severity path traversal vulnerability in Sanster IOPaint, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Sanster IOPaint 1.5.3. Impacted is the function _get_file of the file iopaint/file_manager/file_manager.py of the component File Manager. Performing a manipulation of the argument filename results in path traversal. The attack is possible to be carried out remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

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


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

No fix has been published for CVE-2026-5258 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5258 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5258 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5258 is a medium-severity path traversal vulnerability in Sanster IOPaint, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5258 exists.

Affected product: Sanster IOPaint. 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-5258/ (Markdown: https://insights.sbomify.com/CVE-2026-5258/index.md)
```

## Sources

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

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