Quick answers
- Is CVE-2026-44451 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44451 being exploited in the wild.
- How severe is CVE-2026-44451?
- Critical severity, with a CVSS score of 9.3, published 26 May 2026.
- Which products and versions are affected?
- Prolix-Oc Lumiverse < 0.9.7.
- Is there a fix for CVE-2026-44451?
- A patch was published on 2026-05-26: Fix confirmed 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-44451 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44451?
- Check whether you run 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
The Lumiverse component override system attempts to sandbox user-supplied TSX by transpiling it via Sucrase and evaluating it with 'new Function' while shadowing dangerous globals (like window and fetch) with undefined. It also employs a static source validator (validateComponentOverrideSource) to block forbidden identifiers using regex. These controls are bypassed using two methods: first, string concatenation (e.g., 'ownerDoc' + 'ument') evades the static regex validator; second, by using 'useRef' and 'useEffect' hooks, an attacker can obtain a live DOM node and traverse to the real 'window' object via 'node.ownerDoc.defaultView'. This allows the attacker to bypass all shadowed globals and execute arbitrary code in the context of the victim's authenticated session. The vulnerability is fixed in version 0.9.7.
Affected products
- prolix-oc Lumiverse < 0.9.7
Timeline
- 2026-05-06: advisory: GitHub Security Advisory published by vendor
- 2026-05-26: disclosed: CVE published to NVD
- 2026-05-26: patched: Fix confirmed in version 0.9.7