Vulnary
← back to the feed
Critical· 9.9official fix available

CVE-2026-44450

Lumiverse AI chat application versions before 0.9.7 allow logged‑in users to run arbitrary code on the server by passing unvalidated arguments to allowed binaries. The flaw can be exploited over the network and gives attackers full control of the host.

publishedMay 26, 2026
last modifiedJul 24, 2026
sourcesNVD
severity · cvss
9.9
critical · how bad it is
exploitation · epss
<1%
30th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 24, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Lumiverse AI chat application, any version earlier than 0.9.7, for users who are logged in and have network access to the server.

02

Real-world impact

An attacker can execute arbitrary commands on the Lumiverse server, potentially taking over the machine, stealing data, or using it for further attacks.

03

Why this severity

The CVSS score of 9.9 reflects that the vulnerability can be exploited remotely with low effort, requires only that the user be authenticated, and gives the attacker full confidentiality, integrity, and availability compromise. The scope change indicates that the flaw can affect other components beyond the vulnerable one.

04

What to do about it

official fix available
recommended steps
  1. 01Check the current Lumiverse version running on the server.
  2. 02Download the latest release (0.9.7 or newer) from the official source.
  3. 03Install or upgrade the application to the new version.
  4. 04Restart the Lumiverse service to apply the update.
  5. 05Verify that the server is no longer listening on all interfaces or that host‑header checks are enforced.

NVD-referenced vendor advisory

05

Timeline

  1. May 26, 2026 · May 26, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 24, 2026 · 11d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 25, 2026 · 10d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Privileges requiredLow
User interactionNone needed
ScopeChanged
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →