Path TraversalWeakness · CWE-22

CVE-2026-5258

HIGH · 7.3 CVSS v3.1 Published 2026-04-01

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

82/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · high confidence

A path traversal vulnerability exists in the _get_file function of IOPaint's File Manager component (iopaint/file_manager/file_manager.py). The filename parameter is not properly validated, allowing attackers to use '../' sequences to access files outside the intended directory.

MitigationImplement strict path validation in the _get_file function to ensure the requested file path remains within allowed directories. Use os.path.realpath() to resolve symbolic links and validate the final path is within the permitted directory tree.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: None
User interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify if IOPaint is installed

Run 'pip show iopaint' or check your package manager for the iopaint package installation status

Affected if iopaint is not installed or not found in the environment
Determine the installed IOPaint version

Run 'pip show iopaint' and note the Version field, then compare it against any official version releases of IOPaint that include the fix for this path traversal issue

Affected if the installed version predates the patch for CVE-2026-5258 or no patch version is available
Locate the file_manager.py component

Check for the presence of iopaint/file_manager/file_manager.py in your installation directory - common paths include site-packages/iopaint/file_manager/ or the source directory where IOPaint is installed

Affected if the file_manager.py file exists and contains the _get_file function, indicating the vulnerable component is present
Verify the file manager is exposed or accessible

Check if the File Manager feature is enabled in your IOPaint configuration or running instance - look for file_manager settings in config files or environment variables that enable this component

Affected if the File Manager component is enabled and accessible via API, web interface, or other entry points in your deployment
Inspect the _get_file function for path validation

Examine the source code of the _get_file function in file_manager.py and look for lack of validation on the filename parameter - specifically check if '../' sequences are being sanitized or if os.path.realpath() is used to validate the final path

Affected if the function does not perform proper path validation and allows relative path traversal sequences

You are affected if IOPaint is installed with a vulnerable version containing the unpatched _get_file function and the File Manager component is accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Implement strict path validation in the _get_file function to ensure the requested file path remains within allowed directories. Use os.path.realpath() to resolve symbolic links and validate the final path is within the permitted directory tree.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-5258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5258 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2026-5258?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.3 High

Exploit likelihood EPSS, next 30 days 0.6%

Remediation

A high-priority fix

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-5258 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References