Quick answers
- Is CVE-2026-44449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44449 being exploited in the wild.
- How severe is CVE-2026-44449?
- Critical severity, with a CVSS score of 9.1, published 26 May 2026.
- Which products and versions are affected?
- Lumiverse-Backend <= 0.9.5; Prolix-Oc Lumiverse < 0.9.7.
- Is there a fix for CVE-2026-44449?
- A patch was published on 2026-05-26: Fix released in version 0.9.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44449 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44449?
- Check whether you run Lumiverse-Backend or Prolix-Oc Lumiverse at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A command injection vulnerability exists in the SMBFileSystem.exists() method of Lumiverse. The application attempts to validate paths using toSmbPath(), but if that call fails, it falls back to a dirname/basename split where only the directory component is validated. The unvalidated basename is then concatenated into an smbclient script. An attacker can use the ';' subcommand separator and the '!' local-shell escape character within a filename to execute arbitrary commands on the host. This requires 'Owner' or 'Admin' privileges and is reachable via the connection testing and validation API endpoints. The issue is fixed in version 0.9.7.
Affected products
- prolix-oc Lumiverse < 0.9.7
- npm lumiverse-backend <= 0.9.5
Timeline
- 2026-05-06: advisory: Vendor advisory published on GitHub
- 2026-05-26: disclosed: CVE published to NVD
- 2026-05-26: patched: Fix released in version 0.9.7