CVE-2026-44451: Lumiverse: TSX component sandbox escape via DOM ref and validator bypass

Overview

CVE-2026-44451 is a sandbox escape in the component override feature of Lumiverse, a self-hosted AI chat application. According to the record, user-supplied TSX is transpiled and evaluated at runtime, and the controls meant to restrict it can be circumvented. The record assigns CWE-693 (Protection Mechanism Failure) and a GitHub-sourced CVSS 3.1 base score of 9.3.

Impact

• The record states that the sandbox controls can be bypassed, which would let a malicious component run code with access beyond the intended sandbox.
• The record describes the payload as firing inside the victim's authenticated session. Based on that description, a successful attack could act with the victim's privileges in the application.
• The CVSS vector in the record lists high confidentiality and integrity impact and no availability impact. The scope is listed as changed.

Affected products and versions

• Product: Prolix-oc Lumiverse.
• Affected range: versions before 0.9.7.
• The record's description states the vulnerability is fixed in 0.9.7.
• The record's fixes list is empty. This does not mean no fix exists, because the description names 0.9.7 as the fixed release.

Exploitation status

• The CISA KEV catalog does not list this CVE in the record, so no active exploitation in the wild is confirmed by KEV.
• The SSVC data in the record reports exploitation as 'poc', which indicates that proof-of-concept activity is recognized. The record also marks automatable as 'no'.
• The EPSS probability in the record is 0.00408 with a percentile of 0.33213.
• No confirmed exploitation appears in the sources consulted.

Remediation and mitigation

• Upgrade Lumiverse to version 0.9.7 or later, as stated in the record's description.
• Until patching is possible, review which theme packs (.lumitheme or .lumiverse-theme files) are installed and avoid importing packs from untrusted sources.
• Disable component overrides in the Theme Editor where they are not required, and limit who can import or enable theme packs.
• Consult the GitHub security advisory for vendor guidance and any further details.

Detection guidance

• Inventory Lumiverse deployments and their versions, and flag any instance running a version earlier than 0.9.7.
• Review recently imported theme packs and recently enabled component overrides, especially those received from third parties.
• Monitor application logs and the browser sessions of users who enabled overrides for unexpected behavior after theme import. The record does not describe specific indicators of compromise.

Limitations of the available information

• The record does not describe the exact patch or code changes in 0.9.7.
• The record does not include a fixes list, so the fixed version comes only from the description.
• Vendor advisory details beyond the summary were not available in the record, so the scope of data exposure is unknown.
• The EPSS date in the record is 2026-10-13, which is later than the publication date, so its timing should be verified before relying on it.

Frequently asked questions

Which Lumiverse versions are affected by CVE-2026-44451?

The record lists versions before 0.9.7 as affected, and its description states the issue is fixed in 0.9.7.

Is this CVE known to be actively exploited?

The CISA KEV catalog does not list it in the record, and no confirmed exploitation appears in the sources consulted. The SSVC data reports a proof-of-concept exploitation level.

How can organizations reduce risk before patching?

Review and restrict imported theme packs, disable component overrides where they are not needed, and limit who can enable them until Lumiverse is upgraded to 0.9.7 or later.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.