Public vulnerability disclosure

CVE-2026-44265

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

publishedCWE-20CWE-89CWE-94CWE-749

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.

Technical severity7.4 highCVSS 3.1 · CNA: GitHub_M
Published2026-11-03Source updated 2026-11-03
Collected2026-11-032 attributed sources

Fixes and workarounds

Fix

@enspirit/elo (npm): OSV reports a fixed version 1.0.1. Check the advisory for supported release branches.

Source: OSV GHSA-x9rp-7wh3-2rj5

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
elo
enspirit
< 1.0.1 (affected) CNA: GitHub_M
@enspirit/elo

@enspirit/elo
npm
≥ 0; < 1.0.1 (affected, semver); OSV events: introduced 0; fixed 1.0.1
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "fixed": "1.0.1"
  }
]

Other versions: unaffected
OSV GHSA-x9rp-7wh3-2rj5

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 7.4
high
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HCNA: GitHub_M

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide