Answer in brief
CVE-2026-44265 records a High severity (CVSS 7.4) vulnerability in Elo: Code injection in Elo backends via unvalidated emission of programmatic AST fields. The current sources do not mark it as known exploited. The current feed maps enspirit/elo (generic), @enspirit/elo (npm), @enspirit/elo (npm), @enspirit/elo (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps enspirit/elo (generic), @enspirit/elo (npm), @enspirit/elo (npm), @enspirit/elo (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| enspirit/elogeneric | <1.0.1 | 1.0.1 |
| @enspirit/elonpm | <=1.0.0 | 1.0.1 |
| @enspirit/elonpm | >=0 <1.0.1 | 1.0.1 |
| @enspirit/elonpm | <=1.0.0 | 1.0.1 |
Published upstream
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 3, 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.
Quoted source text, attributed separately from HOL analysis.