Authenticated code execution via MCP stdio arguments
Published May 26, 2026 · Updated May 26, 2026
Argument injection in Lumiverse before 0.9.7 allows remote authenticated users to execute code through crafted MCP stdio arguments. The MCP server creation path allowlists the command basename but passes its args array unchanged to a child process, including inline-code flags. Any logged-in user with network access to the server port can execute code with the Lumiverse server process's operating-system permissions.
Summary
What happened
Argument injection in Lumiverse before 0.9.7 allows remote authenticated users to execute code through crafted MCP stdio arguments. The MCP server creation path allowlists the command basename but passes its args array unchanged to a child process, including inline-code flags. Any logged-in user with network access to the server port can execute code with the Lumiverse server process's operating-system permissions.
The record
- CVE
- CVE-2026-44450
- Published
- May 26, 2026
- Updated
- May 26, 2026
- Vendor
- Prolix OCs
- Product
- Lumiverse
- Classifications
- CWE-88, CAPEC-174, CAPEC-460, CAPEC-41, CAPEC-137, CAPEC-88, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2026CVE publishedPublication date reported by the CVE source.
- May 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.9.7
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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 advisory reproduction stepsproof of concept · demonstrated
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