CVE-2026-44265
7.4HighPublished 03 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Local
- Complexity
- High
- Privileges
- None
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-20, CWE-89, CWE-94, CWE-749
What an attacker gets
Attackers can achieve arbitrary code execution or SQL injection by injecting malicious payloads into the Elo AST API. This requires the application to process untrusted JSON or plugin output through the affected programmatic AST methods.
Root cause
The Elo AST API fails to validate input values before interpolating them into generated code or SQL queries.
Affected versions
Elo prior to 1.0.1
CVSS v3.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade the Elo package to version 1.0.1 or later. If you cannot upgrade immediately, sanitize all input passed to the AST API to ensure no special characters or unexpected syntax are included in literal values or identifiers.
$ npm install elo@1.0.1AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, Elo's programmatic AST API accepts arbitrary values from JSON-deserialized input, plugin output, or other untyped sources and interpolates them into generated JavaScript, Ruby, Python, or SQL without runtime syntax validation. The affected fields are int_literal / float_literal .value, variable.name, member_access.property, object_literal keys, datapath segments, lambda.params[].name, and the SQL let binding name. Crafted values become executable expressions or identifiers, allowing arbitrary code execution in JavaScript, Ruby, and Python targets and SQL injection in the SQL target. This programmatic AST-object path is distinct from the plain-string constructor-chain sandbox escape. This issue is fixed in version 1.0.1.