CVE-2025-43848
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_path0 variable takes user input (e.g. a path to a model) and passes it to the change_info function in process_ckpt.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 confidenceThe ckpt_path0 parameter in Retrieval-based-Voice-Conversion-WebUI accepts user-supplied file paths and passes them directly to the change_info function in process_ckpt.py, which uses torch.load() to load the model. Since torch.load() performs unsafe deserialization of Python objects without validation, an attacker can provide a maliciously crafted 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.
-
Check installed RVC versionLocate the version file or check the web UI version display. Common locations include a version.py file, git tags, or the UI footer. Compare against 2.2.231006.Affected if Installed version is 2.2.231006 or lower.
-
Identify process_ckpt.py and inspect torch.load usageFind process_ckpt.py in the project directory. Search for the change_info function and verify how torch.load() is called.Affected if torch.load() is called without the weights_only=True parameter.
-
Verify if ckpt_path0 parameter accepts arbitrary file pathsInspect the web interface or API endpoint that handles the ckpt_path0 parameter. Check if there is any input validation restricting paths to an allowlist or trusted directory.Affected if ckpt_path0 accepts full filesystem paths without validation or path restrictions.
-
Check web UI accessibilityDetermine if the RVC web interface is exposed to untrusted networks or allows unauthenticated access.Affected if The interface is accessible from untrusted networks without authentication.
You are affected if your installed RVC version is 2.2.231006 or lower AND the ckpt_path0 parameter can accept arbitrary file paths from users, AND torch.load is used without weights_only=True.
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, avoid loading model files from untrusted sources and implement input validation to restrict ckpt_path0 to expected paths. If possible, use torch.load with weights_only=True or implement a safe loading mechanism that validates the model file before deserialization.
- Restrict network access to the Retrieval-Based Voice Conversion WebUI interface - do not expose it to the public internet or untrusted networks
- If the application must be network-accessible, place it behind a properly configured firewall or reverse proxy with authentication
- Implement network segmentation to isolate the voice conversion service from sensitive systems
- Ensure the server running this application follows the principle of least privilege
- Monitor for any suspicious network activity or unauthorized access attempts
- Consider implementing additional input validation at a proxy or application layer to sanitize file paths before they reach the vulnerable function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2025-43848 — 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-43848 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