# CVE-2026-44449: Lumiverse: SMB `exists()` basename injection via smbclient `!cmd` escape

> Attackers can execute arbitrary commands on the Lumiverse server by injecting shell escapes into SMB file paths due to insufficient validation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 27 May 2026

## What is CVE-2026-44449?

CVE-2026-44449 is a critical command injection vulnerability in prolix-oc Lumiverse, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Lumiverse is a full-featured AI chat application. Prior to 0.9.7, when the primary toSmbPath(fullPath) call throws, the method falls back to a dirname/basename split and only validates the directory prefix. The basename is concatenated directly into the smbclient -c script without validation. smbclient interprets ; as a subcommand separator and !cmd as a local-shell escape that runs cmd on the host. A path whose directory component is clean but whose basename contains "; !<cmd>; echo " achieves arbitrary command execution on the Lumiverse server. This vulnerability is fixed in 0.9.7.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-44449?


## How do I fix CVE-2026-44449?

No fix has been published for CVE-2026-44449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44449 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44449 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44449 and fix it if it is affected.

What it is: CVE-2026-44449 is a critical command injection vulnerability in prolix-oc Lumiverse, published on 26 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44449 exists.

Affected product: prolix-oc Lumiverse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44449/ (Markdown: https://insights.sbomify.com/CVE-2026-44449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44449
- OSV: https://osv.dev/vulnerability/CVE-2026-44449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44449/
Summaries are generated and may contain mistakes; the official description above is the record.