CVE-2025-49840
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 · uneditedGPT-SoVITS-WebUI is a voice conversion and text-to-speech webUI. In versions 20250228v3 and prior, there is an unsafe deserialization vulnerability in inference_webui.py. The GPT_dropdown variable takes user input and passes it to the change_gpt_weights function. In change_gpt_weights, the user input, here gpt_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 confidenceThis is an unsafe deserialization vulnerability in GPT-SoVITS-WebUI where the GPT_dropdown parameter takes user input that flows directly to the change_gpt_weights function. The gpt_path user input is passed to torch.load without sanitization, allowing attackers to execute arbitrary code by providing a malicious pickled model file.
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<= 20250228v3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GPT-SoVITS-WebUI versionCheck the installed version of Rvc Boss Gpt Sovits Webui in your environment (check package metadata, version file, or git tag)Affected if The version is 20250228v3 or earlier (any version <= 20250228v3)
-
Locate the change_gpt_weights functionSearch for the change_gpt_weights function in the codebase - this is where the unsafe deserialization occursAffected if The function exists and processes user input from GPT_dropdown parameter
-
Verify torch.load usage on gpt_pathInspect the change_gpt_weights function to confirm gpt_path user input is passed to torch.loadAffected if gpt_path is passed directly to torch.load without sanitization
-
Check for weights_only parameterExamine the torch.load call to see if weights_only=True is setAffected if torch.load is called without weights_only=True parameter (allowing arbitrary pickle deserialization)
You are affected if you are running GPT-SoVITS-WebUI version 20250228v3 or earlier and the application loads model files via torch.load without the weights_only=True parameter or input validation on the gpt_path parameter.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUntil an official patch is available, implement input validation on model paths and use torch.load with weights_only=True parameter or a custom unpickler that restricts dangerous operations. Consider sandboxing model loading in an isolated process.
- Monitor the official GitHub repository (github.com) and security advisories for the release of a patched version
- If exposed to untrusted networks, restrict access to the GPT-SoVITS-WebUI interface via network segmentation or firewall rules
- Implement additional authentication/authorization layers in front of the web interface to limit exposure to trusted users only
- Consider implementing temporary input validation on gpt_path to ensure it points to expected model directories, though this is not a complete fix for unsafe deserialization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation10.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49840 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-49840 in production — separate from our analysis above.
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.
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.
- 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