dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-8755

HIGH · 7.3 CVSS v3.1 Published 2026-05-17
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 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.

NVD · unedited
A flaw has been found in fishaudio Bert-VITS2 up to 8f7fbd8c4770965225d258db548da27dc8dd934c. The affected element is the function _get_all_models of the file hiyoriUI.py of the component Model Handler. This manipulation causes path traversal. The attack can be initiated remotely. The exploit has been published and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

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.

dbcve analysis · high confidence

A path traversal vulnerability exists in the _get_all_models function within hiyoriUI.py of the fishaudio Bert-VITS2 project. This allows remote attackers to access files outside the intended directory through specially crafted path inputs in the Model Handler component. The vulnerability has a CVSS score of 7.3 and an exploit is publicly available.

MitigationImplement strict input validation and path sanitization in the _get_all_models function to ensure all file paths resolve within the intended directory. Consider using canonical path resolution and deny-list or allow-list filtering for file access.

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

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.

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? 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.

dbcve checks

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

  1. Locate hiyoriUI.py in the environment
    Search for the file hiyoriUI.py within the fishaudio Bert-VITS2 project directory structure. Common paths include the root project directory or a ui/ subdirectory.
    Affected if The file hiyoriUI.py exists in the deployed environment
  2. Verify the _get_all_models function exists
    Open hiyoriUI.py and search for a function definition named _get_all_models. Use 'grep -n "_get_all_models" hiyoriUI.py' or open the file in a text editor.
    Affected if The _get_all_models function is present in the code
  3. Confirm Model Handler component is enabled
    Determine if the Model Handler component that calls _get_all_models is active. Check if the UI or API endpoint that uses this function is exposed or running.
    Affected if The Model Handler component is enabled and accessible
  4. Check for lack of path sanitization in _get_all_models
    Review the _get_all_models function code. Look for path validation logic such as os.path.realpath(), os.path.abspath(), or allow-list/deny-list checks that restrict file access to the intended directory.
    Affected if The function lacks proper path sanitization or canonical path resolution
  5. Compare installed version to known affected versions
    Check the installed version of fishaudio Bert-VITS2. Look for version tags in git repository, setup.py, or __version__ variables.
    Affected if The installed version is prior to any available patch addressing this vulnerability

If hiyoriUI.py with the vulnerable _get_all_models function exists, the Model Handler component is enabled, and the function lacks path sanitization, the environment is affected by this path traversal vulnerability.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and path sanitization in the _get_all_models function to ensure all file paths resolve within the intended directory. Consider using canonical path resolution and deny-list or allow-list filtering for file access.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8755 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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