Quick answers
- Is CVE-2026-44444 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44444 being exploited in the wild.
- How severe is CVE-2026-44444?
- Critical severity, with a CVSS score of 9.1, published 26 May 2026.
- Which products and versions are affected?
- Prolix-Oc Lumiverse < 0.9.7.
- Is there a fix for CVE-2026-44444?
- 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-44444 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44444?
- 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
The Spindle extension build pipeline in Lumiverse fails to use the --ignore-scripts flag when executing 'bun install' during the extension installation or update process. This occurs in the manager service before the static backend safety scan (assertSafeBackendBundle) is performed. An attacker with administrative privileges can provide a malicious extension containing lifecycle hooks (such as preinstall or postinstall) in the package.json file. These scripts are executed with the privileges of the server process, leading to host-level remote code execution (RCE). The vulnerability is fixed in version 0.9.7 by ensuring scripts are ignored during the build process.
Affected products
- prolix-oc Lumiverse < 0.9.7
Timeline
- 2026-05-06: advisory: Original GitHub security advisory published
- 2026-05-26: disclosed: CVE published to NVD