dbcve.org
CWE-88Weakness · CWE-88

CVE-2026-44450

CRITICAL · 9.9 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 →
100/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 MCP server creation endpoint validates the command field against an allowlist of binary names but forwards the args array to the child process without any validation. Every binary on the allowlist accepts an inline-code execution flag (-e for node/bun, -c for python3/deno), giving any logged-in user arbitrary OS-level code execution on the Lumiverse server. The route requires only requireAuth (not requireOwner). The server binds on all interfaces (::) and the host-header rebinding check is bypassed trivially by any HTTP client that sends Host: localhost:<port> directly, making this exploitable from any machine with network access to the server port. 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

Lumiverse AI chat application before v0.9.7 contains an authenticated remote code execution vulnerability. The MCP server creation endpoint validates allowed binary names (node, bun, python3, deno) but passes unsanitized arguments to these binaries. Since all allowed binaries support inline code execution flags (-e or -c), any authenticated user can execute arbitrary OS commands. The flaw is exacerbated by the endpoint binding to all interfaces and a trivially bypassable host-header check, enabling remote exploitation from any network-accessible location.

MitigationImmediately upgrade to Lumiverse v0.9.7 or later. If immediate patching is not feasible, disable the MCP server creation endpoint at the network level, restrict server access via firewall rules to trusted IPs only, and implement additional authentication/authorization controls beyond the base requireAuth requirement.

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
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Lumiverse installation and version
    Locate the Lumiverse installation directory and check the version manifest or package.json file. Compare the installed version against the fixed version 0.9.7.
    Affected if The installed version is lower than 0.9.7.
  2. Verify MCP server creation endpoint is accessible
    Identify the API endpoint for MCP server creation (typically /api/mcp/servers or similar). Confirm the endpoint responds to HTTP requests.
    Affected if The MCP server creation endpoint is reachable and accepts requests.
  3. Check network binding configuration
    Examine the Lumiverse network configuration files or running process to determine which network interfaces the service binds to (0.0.0.0 indicates all interfaces).
    Affected if The service listens on all network interfaces (0.0.0.0) rather than localhost only.
  4. Confirm authentication is enforced on the endpoint
    Test the MCP server creation endpoint without valid credentials to determine if authentication is required.
    Affected if The endpoint accepts requests without valid authentication tokens.

You are affected if running Lumiverse version lower than 0.9.7 with the MCP server creation endpoint exposed and accessible, particularly if network binding is set to all interfaces or authentication is not enforced.

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

Immediately upgrade to Lumiverse v0.9.7 or later. If immediate patching is not feasible, disable the MCP server creation endpoint at the network level, restrict server access via firewall rules to trusted IPs only, and implement additional authentication/authorization controls beyond the base requireAuth requirement.

Recommended fix High confidence

0.9.7

  1. Upgrade Lumiverse to version 0.9.7 or later to remediate the argument injection vulnerability

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44450 — 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-44450 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