CVE-2026-63766 RVC-Boss CVE debrief

Who should care

Defenders responsible for GPT-SoVITS deployments should assess exposure and apply remediation. Security teams should prioritize verification of affected versions and implement compensating controls to prevent OS command injection.

Why it matters

CVE-2026-63766 is a critical OS command injection vulnerability in GPT-SoVITS through version 20250606v2pro, allowing unauthenticated attackers to execute arbitrary OS commands. Defenders should assess exposure, verify affected versions, and implement compensating controls to prevent exploitation.

• Unauthenticated OS command execution as the server process user.
• Potential for attackers to inject shell metacharacters through path parameters.
• Lack of specific remediation steps or affected versions in the corpus.
• Need for defenders to verify exposure and apply compensating controls.

Technical summary

The vulnerability is caused by the interpolation of unsanitized Gradio textbox values directly into shell commands executed with shell=True in the webui.py file of GPT-SoVITS through version 20250606v2pro. This allows attackers to inject shell metacharacters through path parameters and execute arbitrary OS commands as the server process user without authentication. Defenders should assess exposure, verify affected versions, and implement compensating controls to prevent exploitation. The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions.

Defensive priority

High priority for defenders to assess exposure and apply remediation, as the vulnerability allows for unauthenticated OS command execution.

Recommended defensive actions

• Assess exposure by checking if GPT-SoVITS versions through 20250606v2pro are in use.
• Verify if the vendor has provided remediation or patches for the vulnerability.
• Implement compensating controls, such as input validation and sanitization, to prevent OS command injection.
• Monitor for potential exploitation attempts and track relevant logs.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish specific versions or remediation steps, which require verification from official sources.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.