dbcve.org
CWE-693Weakness · CWE-693

CVE-2026-44451

CRITICAL · 9.3 CVSS v3.1 Published 2026-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Lumiverse is a full-featured AI chat application. Prior to 0.9.7, the component override system transpiles user-supplied TSX via Sucrase and evaluates it with new Function, shadowing dangerous globals (fetch, window, eval, etc.) with undefined. A static source validator (validateComponentOverrideSource) additionally blocks these identifiers by word-boundary regex. Both controls are bypassed. String-split bypass of the static validator: any blocked identifier can be reconstructed at runtime from string fragments ('ownerDoc' + 'ument'). DOM ref escape from the sandbox: useRef and useEffect are provided in scope. A ref attached to a rendered element gives a live DOM node. From any real DOM node, node['ownerDoc'+'ument']['def'+'aultView'] yields the real window, bypassing all identifier shadows. Theme packs (.lumitheme / .lumiverse-theme) are the shareable delivery mechanism. A malicious pack is an exploit path: the victim imports the file, enables one component override in the Theme Editor, and the payload fires in their authenticated session.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 confidence

Lumiverse's component override system allows users to supply TSX code that gets transpiled with Sucrase and evaluated via new Function. The app attempts to sandbox this by shadowing dangerous globals and using regex to block identifiers, but both controls are bypassed: identifiers can be reconstructed from string fragments, and useRef provides access to live DOM nodes from which the real window is accessible via ownerDocument.defaultView. Malicious theme packs (.lumitheme/.lumiverse-theme) serve as the delivery vector.

MitigationUpgrade to version 0.9.7 or later. Audit imported theme packs for suspicious component overrides and invalidate any session tokens that may have been compromised.

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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Lumiverse version
    Locate the installed Lumiverse package (typically in node_modules/lumiverse or via 'npm list lumiverse') and verify the version number against 0.9.7
    Affected if The installed version is lower than 0.9.7
  2. Identify if component overrides are enabled
    Inspect your Lumiverse configuration files (.lumiconfig or equivalent) for any component override definitions or the 'componentOverrides' setting
    Affected if Component overrides are enabled and pointing to custom or third-party .lumitheme files
  3. Audit imported theme packs
    Review all .lumitheme files being loaded into the application, checking their source and integrity
    Affected if Any .lumitheme file originates from an untrusted or external source
  4. Inspect for useRef DOM access patterns
    Search theme pack TSX files for patterns like 'useRef' combined with 'ownerDocument' or 'defaultView' access, or string-concatenated identifier patterns that may bypass static validation
    Affected if Theme pack code contains useRef usage with subsequent traversal to ownerDocument/defaultView, or string-split constructs reconstructing sensitive identifiers

You are affected if running Lumiverse below 0.9.7 with component overrides enabled that load theme packs, especially from external or untrusted sources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 0.9.7 or later. Audit imported theme packs for suspicious component overrides and invalidate any session tokens that may have been compromised.

Recommended fix High confidence

0.9.7

  1. Upgrade Lumiverse to version 0.9.7 or later to remediate this vulnerability.
  2. Review any custom theme packs (.lumitheme or .lumiverse-theme files) before importing them, as malicious theme packs can trigger the exploit when a component override is enabled in the Theme Editor.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44451 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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