Threat Feed

CVE-2026-44267: enspirit elo · Remote code execution

Exploitation: Public exploit · CVSS 9.8 Critical · Unauthenticated · Published 2026-11-03

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.

Enclave's analysis

Elo, a no-code expression language, lets a plain expression string use .constructor.constructor to reach JavaScript's Function. That runs attacker code in the host runtime: Node.js on library, CLI or CI hosts, and the browser on the auto-running playground. It only matters where untrusted Elo text gets compiled. No exploitation is reported and it isn't in KEV. Upgrade to 1.0.1 or later, and stop feeding untrusted input to older versions.

Fix

Upgrade enspirit elo to 1.0.1. No fixed version is listed for elo; follow the vendor advisory.

Affected versions

ProductVulnerableFixed in
elo< 1.0.1Not listed
enspirit elo< 1.0.11.0.1

Seen in 3 sources