CVE-2026-44267: Sandbox Escape in @enspirit/elo via `.constructor` Access Enables Arbitrary Code Execution
What the vulnerability is
CVE-2026-44267 is a sandbox escape in the @enspirit/elo npm package, scoring 9.8 on CVSS. Elo's JavaScript expression emitter fails to filter .constructor member access on user-controlled template or expression input. An attacker who can submit an expression evaluated by Elo can walk from an ordinary object through .constructor to reach the Function constructor or process, breaking out of the intended sandbox and achieving arbitrary code execution in the hosting Node.js (or browser) runtime.
The root cause is classified under CWE-94 (code injection), CWE-693 (protection mechanism failure — the missing constructor filter), and CWE-1336 (improper neutralization of special elements in a template engine).
Affected software
- Vendor/ecosystem: npm
- Package:
@enspirit/elo - Affected versions: ≤ 1.0.0
- Patched version: not yet published at time of disclosure
Exploitation status
CVE-2026-44267 is currently rated PoC public — a proof-of-concept exploit is available, but there is no evidence yet of in-the-wild weaponization or inclusion in CISA's KEV catalog. Defenders should treat this as an active risk window: public PoCs typically precede automated exploitation attempts by days, not weeks, and with no patched version available, compensating controls and detection are the primary mitigations until a fix ships.
How our detection catches it
Our rule set ships across Microsoft Sentinel (KQL), Splunk (SPL), Elastic (EQL), QRadar (AQL), Sumo Logic, Chronicle (YARA-L), and CrowdStrike (CQL), covering three layers:
- Dependency inventory: identifying hosts and applications with a vulnerable
@enspirit/eloversion (≤ 1.0.0) present in package manifests or lockfiles. - Payload detection: flagging template/expression inputs that contain
constructorchain patterns indicative of sandbox-escape attempts against Elo's emitter. - Post-exploitation behavior: correlating anomalous process spawns or outbound network connections originating from a Node.js runtime known to host Elo, consistent with successful code execution following a sandbox escape.
Combining inventory awareness with payload-level and behavioral signals lets the rule catch exploitation attempts even when the specific payload encoding varies, and flags successful compromise via downstream process/network telemetry.
Full detection details
For the complete, ready-to-deploy KQL, SPL, and other SIEM queries, along with investigation guidance and atomic tests, see the full detection page for CVE-2026-44267.