# CVE-2026-44451: Lumiverse: TSX component sandbox escape via DOM ref and string-split identifier bypass

> Attackers can execute arbitrary code in victim sessions by bypassing sandbox restrictions via DOM references and string-splitting in malicious theme packs.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 May 2026
- **Updated:** 27 May 2026

## What is CVE-2026-44451?

CVE-2026-44451 is a critical code injection vulnerability in prolix-oc Lumiverse, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-693 (Protection Mechanism Failure)

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


## How do I fix CVE-2026-44451?

No fix has been published for CVE-2026-44451 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44451 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44451 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44451 and fix it if it is affected.

What it is: CVE-2026-44451 is a critical code injection vulnerability in prolix-oc Lumiverse, published on 26 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44451 exists.

Affected product: prolix-oc Lumiverse. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44451/ (Markdown: https://insights.sbomify.com/CVE-2026-44451/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44451
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44451
- OSV: https://osv.dev/vulnerability/CVE-2026-44451

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44451/
Summaries are generated and may contain mistakes; the official description above is the record.