Deserialization in Invoke-Ai Invoke-Ai/invokeai
CVE-2024-12029
A remote code execution vulnerability exists in invoke-ai/invokeai versions 5.3.1 through 5.4.2 via the /api/v2/models/install API. The vulnerability arises from unsafe deserialization of model files using torch.load without proper validation. Attackers can exploit this by embedding malicious code in model files, which is executed upon loading. This issue is fixed in version 5.4.3.
Vulnerability class: Insecure Deserialization
Published · last modified .
CVSS v3 metric
CVSS v3 base score 9.8 (Critical). Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.060, 93.4th percentile (last changed ); unchanged over 30 days. About EPSS.
Affected products
- Invoke-Ai Invoke-Ai/invokeai — versions unspecified
Weakness classification (CWE)
Public exploits and proof-of-concept code
Metasploit modules
1 public repository with exploit or proof-of-concept code for this CVE:
- Lu3ky13/Alternative-Approach-Reverse-Shell-Callback-Test-InvokeAI-RCE (last pushed 2026-04-15): This repository contains alternative payload approaches for the InvokeAI RCE vulnerability (CVE-2024-12029) when SSH key injection fails. The payloads are designed to test if pickle deserialization i…
Also mentioned in 2 other repositories (ARPSyndicate/cve-scores, cheshie/code-analysis). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
This CVE has public exploit evidence. See the latest CVEs with public exploits.