Arbitrary code execution via unrestricted class path
Published Aug 25, 2026 · Updated Aug 26, 2026
Code injection in Gemelo AI Vocos 0.1.0 and earlier allows remote attackers to execute arbitrary code through a malicious model repository. instantiate_class in vocos/pretrained.py imports the configuration's unrestricted class_path, resolves it with getattr, and invokes the callable with attacker-supplied init_args. Execution requires an application user to load an attacker-controlled configuration or select a model repository the attacker controls.
Summary
What happened
Code injection in Gemelo AI Vocos 0.1.0 and earlier allows remote attackers to execute arbitrary code through a malicious model repository. instantiate_class in vocos/pretrained.py imports the configuration's unrestricted class_path, resolves it with getattr, and invokes the callable with attacker-supplied init_args. Execution requires an application user to load an attacker-controlled configuration or select a model repository the attacker controls.
The record
- CVE
- CVE-2026-79784
- Published
- Aug 25, 2026
- Updated
- Aug 26, 2026
- Vendor
- Gemelo AI
- Product
- Vocos
- Classifications
- CWE-470, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 25, 2026CVE publishedPublication date reported by the CVE source.
- Aug 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.1.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 76 minimal reproductionproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo