CVE-2026-44444
Deferred Deferred - Pending Action
Code Execution via Preinstall Script in Lumiverse AI Chat

Publication date: 2026-05-26

Last updated on: 2026-05-27

Assigner: GitHub, Inc.

Description
Lumiverse is a full-featured AI chat application. Prior to 0.9.7, the Spindle extension build pipeline calls bun install without the --ignore-scripts flag before running the static backend safety scan (assertSafeBackendBundle). A malicious extension that ships a package.json with a preinstall, postinstall, or prepare lifecycle script achieves host-level code execution the moment an admin presses Install before any dist file is inspected. This vulnerability is fixed in 0.9.7.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-26
Last Modified
2026-05-27
Generated
2026-06-16
AI Q&A
2026-05-27
EPSS Evaluated
2026-06-14
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
lumiverse lumiverse to 0.9.7 (exc)
lumiverse spindle to 0.9.7 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-78 The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability exists in Lumiverse, an AI chat application, specifically in versions prior to 0.9.7. The issue arises in the Spindle extension build pipeline, where the process calls 'bun install' without the '--ignore-scripts' flag before running a backend safety scan. Because of this, a malicious extension containing lifecycle scripts like preinstall, postinstall, or prepare in its package.json can execute code on the host system as soon as an admin clicks Install, even before any files are inspected.

Impact Analysis

This vulnerability can lead to host-level code execution, meaning an attacker can run arbitrary code on the system where Lumiverse is installed. This can compromise the confidentiality, integrity, and availability of the system and its data, potentially allowing attackers to steal sensitive information, alter data, or disrupt services.

Mitigation Strategies

To mitigate this vulnerability, upgrade Lumiverse to version 0.9.7 or later, where the issue has been fixed.

Avoid installing extensions before verifying their contents, especially any lifecycle scripts such as preinstall, postinstall, or prepare scripts in package.json files.

Compliance Impact

This vulnerability allows an attacker with admin privileges to execute arbitrary code at the OS level on the server hosting the Lumiverse application. Such unauthorized code execution can lead to full compromise of confidentiality, integrity, and availability of data and systems.

Given the critical impact on confidentiality and integrity, this vulnerability could lead to violations of common standards and regulations such as GDPR and HIPAA, which require protection of sensitive personal and health data against unauthorized access and modification.

Specifically, exploitation could result in unauthorized data access, data breaches, or data tampering, all of which are non-compliant with these regulations' requirements for data security and privacy.

Detection Guidance

Detection of this vulnerability involves identifying if the vulnerable versions of Lumiverse (0.9.5 and below) or the Spindle extension are in use, and whether the build pipeline runs the `bun install` command without the `--ignore-scripts` flag.

You can check the version of Lumiverse installed by running commands like:

  • `npm list lumiverse-backend` or `npm ls lumiverse-backend` to see the installed package version.

To detect if the build pipeline runs `bun install` without the `--ignore-scripts` flag, you can search the build scripts or CI/CD pipeline configuration files for the command usage:

  • `grep -r "bun install" ./path-to-build-scripts/`
  • Check if the `--ignore-scripts` flag is missing in the output.

Additionally, you can audit installed extensions for suspicious lifecycle scripts by inspecting their `package.json` files for `preinstall`, `postinstall`, or `prepare` scripts that could execute code:

  • `find ./extensions -name package.json -exec grep -E '"(preinstall|postinstall|prepare)"' {} \;`

Monitoring for unexpected or unauthorized code execution during extension installation or updates can also help detect exploitation attempts.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44444. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart