dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-44444

CRITICAL · 9.1 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Lumiverse application extension build pipeline runs `bun install` without the `--ignore-scripts` flag when installing extensions. This allows malicious extensions containing preinstall, postinstall, or prepare lifecycle scripts in their package.json to achieve host-level code execution immediately upon installation, before any security scan occurs.

MitigationUpgrade to Lumiverse version 0.9.7 or later, which includes the `--ignore-scripts` flag in the bun install command to prevent execution of lifecycle scripts during extension installation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Lumiverse version
    Locate the Lumiverse installation and determine its version number (check application metadata, about dialog, or version file)
    Affected if The installed version is lower than 0.9.7 (e.g., 0.9.6, 0.9.5, etc.)
  2. Verify Spindle extension build pipeline is in use
    Confirm that the Spindle extension build pipeline is enabled or has been used to install extensions in your environment
    Affected if The Spindle pipeline is actively used or configured for extension installations
  3. Inspect build pipeline configuration
    Examine the Spindle build pipeline configuration files or scripts to determine whether 'bun install' is executed without the --ignore-scripts flag before the assertSafeBackendBundle safety scan runs
    Affected if The pipeline runs 'bun install' without --ignore-scripts and performs the safety scan after installation rather than before
  4. Review recent extension installations
    Check logs or audit records for any extension installations that occurred using the vulnerable pipeline version
    Affected if Any extensions were installed using Lumiverse versions prior to 0.9.7 through the Spindle pipeline

You are affected if Lumiverse is installed at a version prior to 0.9.7 and the Spindle extension build pipeline has been used to install extensions without --ignore-scripts being passed to bun install.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Lumiverse version 0.9.7 or later, which includes the `--ignore-scripts` flag in the bun install command to prevent execution of lifecycle scripts during extension installation.

Recommended fix High confidence

0.9.7

  1. Upgrade Lumiverse to version 0.9.7 or later to obtain the patch that adds the --ignore-scripts flag when running bun install in the Spindle extension build pipeline
  2. After upgrading, verify that the Spindle extension build pipeline now runs bun install --ignore-scripts before calling assertSafeBackendBundle
  3. Test the extension installation process to confirm that malicious lifecycle scripts (preinstall, postinstall, prepare) are blocked from executing during the install phase

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
14.0 hours of engineering $2,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44444 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44444 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data