CVE-2025-43846
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_path1 variable takes user input (e.g. a path to a model) and passes it to the show_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 confidenceRetrieval-based-Voice-Conversion-WebUI versions 2.2.231006 and prior are vulnerable to unsafe deserialization via torch.load. The ckpt_path1 parameter accepts user-supplied model file paths and passes them to the show_info function in process_ckpt.py, which loads the model using torch.load without sanitization. Maliciously crafted model files can contain serialized Python objects that execute arbitrary code during deserialization, leading to 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 Retrieval-based-Voice-Conversion-WebUI installationLocate the application directory (commonly named 'Retrieval-based-Voice-Conversion-WebUI', 'RVC', or 'rvc-webui') and confirm the product exists on the systemAffected if The application is installed and the directory contains process_ckpt.py
-
Determine installed versionCheck the version file, git tags, or pip package metadata within the application directory. Common locations: version.py, __init__.py, or run 'git describe --tags' if it's a git repositoryAffected if The version is 2.2.231006 or prior
-
Locate vulnerable code in process_ckpt.pyFind the file process_ckpt.py in the application codebase and inspect the show_info function for direct torch.load() calls on the ckpt_path1 parameter without weights_only=TrueAffected if The file exists and contains torch.load(ckpt_path1) or similar without weights_only=True validation
-
Verify web interface exposureCheck if the web application is bound to a network interface accessible to untrusted users (listen on 0.0.0.0 or publicly accessible IP versus localhost only)Affected if The web interface is accessible to untrusted network callers
-
Confirm parameter handling vulnerabilityReview the code path that handles the ckpt_path1 parameter from HTTP requests to torch.load() to verify user-supplied file paths reach the deserialization without validationAffected if User-controllable input flows directly to torch.load() without sanitization
You are affected if the application is installed with version 2.2.231006 or prior and the vulnerable process_ckpt.py code with unsafe torch.load() is exposed to untrusted users.
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.
From vendor dataSince no vendor patch exists, implement input validation to restrict ckpt_path1 to trusted/whitelisted paths only, and modify torch.load calls to use weights_only=True or replace with safer deserialization methods. Isolate the service network-wise to limit exposure.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.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 $8,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43846 — 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-43846 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