CVE-2025-43850
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 · uneditedRetrieval-based-Voice-Conversion-WebUI is a voice changing framework based on VITS. Versions 2.2.231006 and prior are vulnerable to unsafe deserialization. The ckpt_dir variable takes user input (e.g. a path to a model) and passes it to the change_info function in export.py, which uses it to load the model on that path with torch.load, which can lead to unsafe deserialization and remote code execution. As of time of publication, no known patches exist.
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 confidenceRetrieval-based-Voice-Conversion-WebUI versions 2.2.231006 and prior contain an unsafe deserialization vulnerability in the change_info function in export.py. The ckpt_dir parameter accepts user-supplied file paths which are passed directly to torch.load() without validation. Since torch.load() deserializes Python objects from pickle files, an attacker can provide a malicious model file to achieve remote code execution.
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<= 2.2.231006CVSS 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 if Rvc Project Webui is installedLocate the project directory - look for a folder named 'RVC' or similar containing the WebUI for Retrieval Based Voice Conversion. Check for export.py in the project root or source directory.Affected if The Rvc Project Retrieval Based Voice Conversion Webui software is present on the system.
-
Locate the vulnerable export.py fileSearch for export.py in the project directory. The vulnerability exists in the change_info function within this file.Affected if export.py exists in the RVC project and contains a change_info function that handles model loading.
-
Inspect torch.load usage in change_info functionOpen export.py and locate the change_info function. Examine all torch.load calls within this function to see if the weights_only parameter is used.Affected if torch.load is called without weights_only=True parameter in the change_info function.
-
Verify ckpt_dir user input flows to torch.loadIn export.py, trace how the ckpt_dir variable (user-supplied input) is used. Confirm it is passed directly to torch.load without sanitization.Affected if The ckpt_dir variable receives user input and passes it directly to torch.load without weights_only protection.
-
Check installed software versionLook for version information in the project - check VERSION file, setup.py, or git tags. The affected version is <= 2.2.231006.Affected if The installed version is 2.2.231006 or earlier.
A user is affected if they have Rvc Project Webui installed with export.py containing torch.load calls without weights_only parameter in the change_info function, allowing user-controlled ckpt_dir to flow directly to the unsafe torch.load.
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 released, implement input validation on the ckpt_dir parameter to restrict paths to an allowlist, and modify torch.load() calls to use weights_only=True (if compatible) or implement custom safe unpickling logic. Network-accessible model loading interfaces should be restricted or disabled.
- Do not expose the affected voice conversion functionality to untrusted or external network sources until a vendor patch is released.
- If the ckpt_dir parameter can be controlled by users, restrict or disable this input mechanism to prevent malicious model file loading.
- Implement network-level access controls to limit who can interact with the webui.
- Monitor for any suspicious activity related to model file loading or unusual network requests.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43850 — 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-43850 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