Vulnerability in Lumiverse (CVE-2026-44449)
Summary
Vulnerability in Lumiverse (CVE-2026-44449). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 0.9.7 or later.
Original description
The description as published by the source.
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 "; !; echo " achieves arbitrary command execution on the Lumiverse server. This vulnerability is fixed in 0.9.7.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-44449 has been found in Lumiverse.
Successful exploitation can lead to full system takeover. CVSS score: 9.1/10.
What to do: upgrade Lumiverse to 0.9.7 or later.
If unsure, ask your IT team or search "Lumiverse CVE-2026-44449" on the vendor's site.
CVE-2026-44449 (Lumiverse) — CWE-88 / CVSS v3 9.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 0.9.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-88) exists in Lumiverse.
Check the vendor advisory for the affected versions of Lumiverse.
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover.
Update to 0.9.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Lumiverse' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Lumiverse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Lumiverseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Lumiverse to 0.9.7ステージング環境で 0.9.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web github.com