Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-33r5-xmm8-v6x5 | Elo JavaScript emitter has sandbox escape to arbitrary Node.js / browser code execution via unfiltered `.constructor` member access |
Tue, 03 Nov 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, plain Elo strings supplied to defaultFormats.elo.parse(), bin/elo, or elo-lang.org/try can use .constructor.constructor to reach JavaScript Function because the member_access handler in src/transform.ts does not reject meta-properties, src/compilers/javascript.ts emits the surviving property directly, and src/parser.ts accepts constructor as an ordinary identifier. The resulting generated JavaScript executes attacker-selected code in the host runtime. This permits browser script execution and session compromise on the auto-running playground and arbitrary Node.js code execution on library, CI, or DevOps hosts. This plain-string path is distinct from the programmatic AST-object injection issue. This issue is fixed in version 1.0.1. | |
| Title | Elo: Sandbox escape to arbitrary Node.js / browser code execution via unfiltered `.constructor` member access in Elo JavaScript emitter | |
| Weaknesses | CWE-1336 CWE-693 CWE-79 CWE-94 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-03T17:52:25.509Z
Reserved: 2026-05-05T16:33:55.845Z
Link: CVE-2026-44267
No data.
Status : Received
Published: 2026-11-03T18:18:03.130
Modified: 2026-11-03T18:18:03.130
Link: CVE-2026-44267
No data.
OpenCVE Enrichment
Updated: 2026-11-03T20:15:14Z
Github GHSA