CVE Intelligence
Analysis AI-assisted

CVE-2026-44444: Lumiverse Spindle: extension install runs lifecycle scripts before safety scan

CVE-2026-44444 affects Lumiverse versions before 0.9.7. The Spindle extension build pipeline runs bun install without ignoring lifecycle scripts before the backend safety scan, so a malicious extension can execute code on the host when an administrator starts its install. The record rates it critical with CVSS 3.1 score 9.1, and no confirmed exploitation appears in the sources consulted.

Published Oct 13, 2026 · Updated Oct 13, 2026 · Ler em português

Overview

Lumiverse is a full-featured AI chat application. According to the record, versions before 0.9.7 run package lifecycle scripts while installing Spindle extensions, before the static backend safety check (assertSafeBackendBundle) inspects the built files. The weakness is classified as CWE-78, OS command injection.

Impact

  • A malicious extension whose package manifest defines preinstall, postinstall or prepare scripts could run code on the host once an administrator starts the install.
  • The record states that this happens before any distributed file is inspected, so the safety scan does not prevent it.
  • The CVSS 3.1 vector lists high confidentiality, integrity and availability impact with scope change. It also lists high privileges required. GitHub is the CNA reporting the score of 9.1.

Affected products and versions

  • Product: Prolix-oc Lumiverse, version < 0.9.7 according to the record.
  • The structured fixes field is empty, but the description states the issue is fixed in 0.9.7.
  • Users on 0.9.7 or later are outside the stated affected range.

Exploitation status

  • The record shows that this CVE is not listed in the CISA KEV catalog.
  • No confirmed exploitation in the wild appears in the sources consulted.
  • The SSVC data in the record reports exploitation as poc and automatable as yes. The EPSS probability is 0.00665 with percentile 0.50472, as recorded.

Remediation and mitigation

  • Upgrade Lumiverse to version 0.9.7 or later, as stated in the record description.
  • Until the upgrade is applied, install Spindle extensions only from sources that are fully trusted and reviewed.
  • Review package manifests of extensions before any install action, looking for lifecycle scripts.
  • Restrict which accounts can trigger extension installation.
  • Consult the vendor advisory GHSA-8x98-3wjp-pmj9 for upstream guidance.

Detection guidance

  • Monitor for unexpected child processes started by the Lumiverse server during extension installation.
  • Audit logs of extension install actions, recording who initiated each action and where the extension came from.
  • Watch the application host for unexpected file changes or outbound connections shortly after an extension install.

Limitations of the available information

  • The record gives only a version range and does not list specific builds or commits.
  • The fixed version appears only in the description text, not in the structured fixes field.
  • The vector lists UI:N (no user interaction), while the description places the trigger on an administrator pressing Install. The record does not resolve this difference.
  • Only one vendor advisory reference is recorded. No independent analysis was consulted.
  • The EPSS date in the record is later than the publication date, so the EPSS values should be checked against the current feed.

Frequently asked questions

Which Lumiverse versions are affected by CVE-2026-44444?

According to the record, versions before 0.9.7 are affected, and the description states the issue is fixed in 0.9.7.

Is this vulnerability being actively exploited?

The record shows it is not listed in the CISA KEV catalog, and no confirmed exploitation appears in the sources consulted.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.