Public vulnerability disclosure

CVE-2026-44266

Elo: Remote Code Execution in Elo Ruby backend via unescaped `#{...}` interpolation in emitted string literals and subtype-constraint labels

publishedCWE-94CWE-116CWE-1336

Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, the Ruby backend in src/compilers/ruby.ts embeds attacker-controlled text in Ruby double-quoted strings without escaping #, so Ruby interpolation forms in the string-literal emitter or the labelled subtype-constraint branch become executable Ruby. The affected entry points include the /try playground with the Ruby target, bin/eloc -t ruby -x, and defaultFormats.elo.parse() followed by Ruby emission. A failing labelled subtype constraint evaluates its message, while an ordinary string literal is evaluated when the compiled Ruby runs, allowing Ruby code and shell command execution through backticks. JavaScript, Python, and SQL emission are not affected by this Ruby-specific path. This issue is fixed in version 1.0.1.

Technical severity9.8 criticalCVSS 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-7w38-ggh5-v542

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-7w38-ggh5-v542

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 / 9.8
critical
CVSS:3.1/AV:N/AC:L/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