CVE-2026-44265 PUBLISHED

Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields

Assigner: GitHub_M
Reserved: 05.05.2026 Published: 03.11.2026 Updated: 03.11.2026

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.

Metrics

CVSS Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS Score: 7.4

Product Status

Vendor enspirit
Product elo
Versions
  • Version < 1.0.1 is affected

References

Problem Types

  • CWE-20: Improper Input Validation CWE
  • CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') CWE
  • CWE-94: Improper Control of Generation of Code ('Code Injection') CWE
  • CWE-749: Exposed Dangerous Method or Function CWE