Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x9rp-7wh3-2rj5 | Elo backends have code injection via unvalidated emission of programmatic AST fields |
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, 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. | |
| Title | Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields | |
| Weaknesses | CWE-20 CWE-749 CWE-89 CWE-94 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-11-03T17:47:03.347Z
Reserved: 2026-05-05T16:33:55.845Z
Link: CVE-2026-44265
No data.
Status : Received
Published: 2026-11-03T18:18:02.760
Modified: 2026-11-03T18:18:02.760
Link: CVE-2026-44265
No data.
OpenCVE Enrichment
Updated: 2026-11-03T19:45:14Z
Github GHSA