CVE-2026-44449
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 · uneditedLumiverse 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.
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 confidenceIn Lumiverse versions prior to 0.9.7, the toSmbPath() function has a fallback path that only validates the directory component of a path while directly concatenating the basename into an smbclient -c script without sanitization. Since smbclient treats ; as a command separator and !cmd as a shell escape, a malicious basename like '; !<cmd>; echo ' enables arbitrary command execution on the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Check Lumiverse installation and versionLocate the Lumiverse installation directory and determine the installed version (e.g., lumiverse --version, check VERSION file, or inspect package metadata). Compare it to version 0.9.7.Affected if The installed version is lower than 0.9.7, indicating the vulnerable code is likely present.
-
Verify SMB functionality is in useIdentify if any part of the application or configuration uses SMB path handling (smb:// URLs or paths passed to toSmbPath()). Review application logs, configuration files, or code that handles SMB operations.Affected if SMB paths are being processed by the toSmbPath() function, which triggers the vulnerable code path.
-
Inspect the toSmbPath() function source codeLocate the toSmbPath() function in the Lumiverse source code (typically in SMB-related modules). Examine whether the fallback code path exists and if it concatenates the basename directly into smbclient -c commands without sanitization.Affected if The code shows the fallback path that validates only the directory prefix but concatenates unsanitized basename into smbclient commands.
-
Check for smbclient command construction patternsSearch the codebase for patterns where smbclient -c is used with string concatenation involving path components. Look for constructs that append basename values directly to the -c argument.Affected if The code directly concatenates path basenames into smbclient -c command strings without using parameterized queries or shell escaping functions.
-
Determine if the primary method can throw exceptionsReview the primary code path in toSmbPath() to identify conditions under which it throws exceptions and triggers the fallback path. This may involve checking for specific SMB server responses, network conditions, or configuration states.Affected if The primary method has error-handling that throws exceptions, making the fallback code path reachable under normal error conditions.
A user is affected if they run Lumiverse version below 0.9.7, use SMB path functionality, and the vulnerable fallback code path in toSmbPath() concatenates unsanitized basenames into smbclient commands.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to Lumiverse version 0.9.7 or later. If immediate upgrade is not possible, implement input validation that sanitizes all path components (especially basename) before passing them to smbclient, blocking characters like ; and !.
0.9.7
- Identify the currently installed Lumiverse version by checking the application binaries, package manager, or deployment configuration
- Backup all Lumiverse data, configuration files, and any custom settings before proceeding
- Obtain Lumiverse version 0.9.7 from the official source (the GitHub repository mentioned in the reference)
- Stop the Lumiverse service to prevent active connections during upgrade
- Upgrade Lumiverse to version 0.9.7 using the standard upgrade procedure for your deployment method (e.g., package manager, manual binary replacement, or container update)
- Verify the upgrade was successful by checking the installed version matches 0.9.7
- Restart the Lumiverse service
- Test that SMB path handling functions correctly with various path inputs to confirm the fix is working
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44449 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44449 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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