dbcve.org
Gpt Sovits WebuiApplication · Rvc Boss

CVE-2025-49841

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-15
Fix available
A fix is available. Upgrade to after 20250228v3 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
GPT-SoVITS-WebUI is a voice conversion and text-to-speech webUI. In versions 20250228v3 and prior, there is an unsafe deserialization vulnerability in process_ckpt.py. The SoVITS_dropdown variable takes user input and passes it to the load_sovits_new function in process_ckpt.py. In load_sovits_new, the user input, here sovits_path is used to load a model with torch.load, leading to unsafe deserialization. At time of publication, no known patched versions are available.

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-WebUI versions 20250228v3 and prior contain an unsafe deserialization vulnerability where user input from the SoVITS_dropdown parameter is passed directly to PyTorch's torch.load() function without sanitization. An attacker can supply a malicious serialized model file path to achieve arbitrary code execution on the target system.

MitigationSince no official patch exists, restrict network access to the webUI interface, implement strict input validation on model file paths using allowlists, and if possible refactor the code to use torch.load with weights_only=True or alternative safe loading methods that avoid arbitrary object deserialization.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gpt Sovits WebuiApplication
Affected:<= 20250228v3

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. Identify GPT-SoVITS-WebUI installation
    Locate the GPT-SoVITS-WebUI application directory or check running processes for the webUI service. Common indicators include the project folder name 'GPT-SoVITS' or 'gpt-sovits-webui' and associated model directories.
    Affected if The application is installed and running on the system.
  2. Determine installed version
    Check the version file, git commit history, or application metadata within the GPT-SoVITS-WebUI directory. Compare against version 20250228v3.
    Affected if The installed version is 20250228v3 or any prior version.
  3. Verify web interface is accessible
    Confirm the web UI service is running and reachable on its configured port (commonly port 9872, 9873, or 5000). Check if the SoVITS model selection functionality is exposed.
    Affected if The web interface is exposed and the SoVITS dropdown parameter can be accessed.
  4. Inspect torch.load usage in source code
    Examine the backend code handling the SoVITS_dropdown parameter. Locate the code path where user input is passed to torch.load(). Verify whether weights_only=True or safe loading methods are implemented.
    Affected if torch.load() is called with user-supplied input without weights_only=True or equivalent sanitization.

A user is affected if GPT-SoVITS-WebUI version 20250228v3 or earlier is installed, the web interface is accessible, and the SoVITS dropdown parameter feeds directly into torch.load() without safe deserialization settings.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 20250228v3
Interim mitigation

Since no official patch exists, restrict network access to the webUI interface, implement strict input validation on model file paths using allowlists, and if possible refactor the code to use torch.load with weights_only=True or alternative safe loading methods that avoid arbitrary object deserialization.

Recommended fix High confidence
  1. No patch is currently available. Monitor the official GitHub repository (github.com) for security updates.
  2. Avoid exposing the SoVITS_dropdown feature to untrusted users or input.
  3. If possible, implement input validation on the sovits_path parameter to restrict paths to trusted model files only.
  4. Consider isolating the application in a sandboxed environment until a patch is released.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gpt Sovits Webui 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 the upgrade done

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-2025-49841 — 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-2025-49841 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