dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-63766

CRITICAL · 9.8 CVSS v3.1 Published 2026-07-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 4 weeks old

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
GPT-SoVITS through 20250606v2pro contains an OS command injection vulnerability in webui.py where ASR, slice, denoise, and uvr5 functions interpolate unsanitized Gradio textbox values directly into shell commands executed with shell=True. Attackers can inject shell metacharacters through path parameters to execute arbitrary OS commands as the server process user without authentication.

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

GPT-SoVITS through 20250606v2pro has an OS command injection vulnerability in webui.py where the ASR, slice, denoise, and uvr5 functions interpolate unsanitized Gradio textbox values directly into shell commands executed using shell=True. Attackers can inject shell metacharacters through path parameters to execute arbitrary OS commands as the server process user without authentication.

MitigationReplace shell=True with shell=False and use argument lists, or implement strict input validation to sanitize path parameters before passing them to subprocess calls.

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
High
Integrity
High
Availability
High

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

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 GPT-SoVITS installation directory
    Search for directories containing 'GPT-SoVITS' or 'webui.py' files on the system. Common locations include /home/*/GPT-SoVITS, /opt/GPT-SoVITS, or the current working directory if cloned from a repository.
    Affected if The application directory cannot be found, meaning GPT-SoVITS is not installed.
  2. Identify installed GPT-SoVITS version
    Check for a version file or git tag in the installation directory. Look for version.py, __version__ variable, or git tags (git tag -l). Compare the version against 'v2pro' to determine if it is v2pro or earlier.
    Affected if The version is v2pro or any earlier version, placing it within the affected range.
  3. Examine webui.py for shell=True with user input
    Open webui.py and search for patterns like 'shell=True' combined with f-string or .format() interpolation of textbox input. Focus on functions named 'ASR', 'slice', 'denoise', or 'uvr5' and verify if Gradio textbox values are directly interpolated into shell commands.
    Affected if The vulnerable pattern exists where unsanitized Gradio textbox input is passed to subprocess with shell=True.
  4. Verify web interface is network-accessible
    Check webui.py for app.launch() calls. Inspect if the interface is bound to 0.0.0.0 or a public IP rather than localhost (127.0.0.1). Review any server configurations or startup scripts that expose the Gradio port.
    Affected if The web interface is accessible from non-localhost addresses, enabling remote exploitation.
  5. Confirm ASR, slice, denoise, and uvr5 functions use vulnerable parameters
    In webui.py, locate the function definitions for ASR, slice, denoise, and uvr5. Identify which parameters accept file paths or text input and trace whether these flow into shell command execution without sanitization.
    Affected if Any of these four functions accept path parameters that are directly interpolated into shell commands with shell=True.

A system is affected if GPT-SoVITS v2pro or earlier is installed, the webui.py file contains the shell=True pattern with unsanitized input in ASR/slice/denoise/uvr5 functions, and the web interface is network-accessible.

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

Replace shell=True with shell=False and use argument lists, or implement strict input validation to sanitize path parameters before passing them to subprocess calls.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-63766 — 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-63766 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