Quick answers
- Is CVE-2026-44450 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44450 being exploited in the wild.
- How severe is CVE-2026-44450?
- Critical severity, with a CVSS score of 9.9, published 26 May 2026.
- Which products and versions are affected?
- Prolix-Oc Lumiverse < 0.9.7.
- Is there a fix for CVE-2026-44450?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-44450 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44450?
- Check whether you run Prolix-Oc Lumiverse at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An argument injection vulnerability exists in the MCP server creation endpoint of Lumiverse. While the application validates the primary command against an allowlist of binaries (e.g., node, python3), it fails to validate the 'args' array passed to the child process. Attackers can use flags like '-e' or '-c' to execute inline code through these allowed binaries. The vulnerability is reachable by any authenticated user (requireAuth) and can be exploited over the network because the server binds to all interfaces and lacks robust host-header validation. This results in full OS-level code execution as the user running the Lumiverse process.
Affected products
- prolix-oc Lumiverse < 0.9.7
- npm lumiverse-backend <= 0.9.5
Timeline
- 2026-05-06: advisory: Original GitHub advisory published
- 2026-05-26: disclosed: CVE published to NVD