CVE-2026-44449
Command Injection in Lumiverse AI Chat Application
Publication date: 2026-05-26
Last updated on: 2026-05-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| lumiverse | lumiverse | to 0.9.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-88 | The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Lumiverse, an AI chat application, in versions prior to 0.9.7. When the primary toSmbPath(fullPath) call fails, the application falls back to splitting the path into directory and basename components and only validates the directory prefix. The basename is then concatenated directly into an smbclient command script without proper validation. Since smbclient interprets a semicolon (;) as a subcommand separator and !cmd as a local shell escape, an attacker can craft a path with a clean directory but a malicious basename containing "; !<cmd>; echo " to execute arbitrary commands on the Lumiverse server.
How can this vulnerability impact me? :
This vulnerability allows an attacker with access to craft malicious paths to execute arbitrary commands on the Lumiverse server. This can lead to full compromise of the server, including unauthorized access, data theft, data modification, or disruption of services. Given the high CVSS score (9.1) and the impact on confidentiality, integrity, and availability, the vulnerability poses a critical risk to affected systems.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability is fixed in Lumiverse version 0.9.7. Immediate mitigation should include upgrading Lumiverse to version 0.9.7 or later to ensure the vulnerable code path is no longer used.