# CVE-2026-44265: Elo code injection via unvalidated AST fields

Source: https://junglewise.ai/threats/cve-2026-44265-elo-backends-have-code-injection-via-unvalidated-emission-of  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-03. Updated: 2026-11-03  
License: CC BY 4.0 with a link back

CVE-2026-44265 · Severity: high · CVSS 7.4 · Published 2026-11-03

Elo is a templating and data-transformation language that compiles to JavaScript, Ruby, Python, and SQL. The programmatic AST API accepts unsanitized values in node fields and emits them directly into generated source code without validation. An attacker who can populate the AST from untrusted input (JSON, plugin output, etc.) can execute arbitrary code or SQL commands on the target system.

Technologies: [@enspirit/elo (npm)](https://junglewise.ai/threats/technologies/enspirit-elo). Vendors: [npm](https://junglewise.ai/threats/vendors/npm).

## Quick answers

**Is CVE-2026-44265 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-44265 being exploited in the wild.

**How severe is CVE-2026-44265?** High severity, with a CVSS score of 7.4, published 3 November 2026.

**Which products and versions are affected?** @enspirit/elo (npm) <= 1.0.0, SEMVER:introduced=0,fixed=1.0.1; Elo before fix.

**Is there a fix for CVE-2026-44265?** Yes. @enspirit/elo (npm): upgrade to 1.0.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-44265 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-44265?** Check whether you run @enspirit/elo (npm) or Elo at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- @enspirit/elo (npm): upgrade to 1.0.1 or later

  ```sh
  npm install @enspirit/elo@1.0.1
  ```


## Technical details

Multiple AST node fields (at least 23 sites across six categories) lack runtime type or syntax validation in the emit stage of all four backends. Vulnerable sinks include numeric literal values, variable names, member access properties, object keys, datapath segments, lambda parameters, and SQL let-binding names. An AST-API consumer that deserializes untrusted input can inject arbitrary expressions into numeric positions, identifiers, property access, and SQL contexts, achieving RCE on JavaScript/Ruby/Python backends and SQL injection on SQL backend.

## Affected products

- Elo before fix

## Identifiers

- CVE-2026-44265
- GHSA-x9rp-7wh3-2rj5

## Timeline

- 2026-11-03: disclosed

## Related threats

- [Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, plain Elo strings supplied to defaultFormats.elo.parse()](https://junglewise.ai/threats/cve-2026-44267-elo-javascript-emitter-has-sandbox-escape-to-arbitrary-node-js)
- [Elo Ruby backend remote code execution via unescaped string interpolation](https://junglewise.ai/threats/cve-2026-44266-elo-ruby-backend-has-remote-code-execution-via-unescaped)