Vulnerabilities

Vulnerability · CVE-2026-44266

Elo Ruby backend has Remote Code Execution via unescaped interpolation in emitted string literals and subtype-constraint labels

Published Nov 3, 2026 · catalog updated Nov 3, 2026 · Elo Ruby backend has

Last checked Nov 8, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2026-44266. EPSS is 1.00%. Act only if a listed version of Elo Ruby backend has is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Elo Ruby backend has).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.00%
Remediation
Version ranges on file
Affected products
npm @enspirit · npm @enspirit/elo

### Summary Elo's Ruby backend emits attacker-controlled text into Ruby double-quoted strings without escaping the character. Because begins Ruby's interpolation sequences — , , , — and any expression wrapped in may use backticks for shell execution, an Elo program that contains a crafted string literal or a labelled subtype constraint compiles to Ruby that evaluates attacker-chosen Ruby, and through backticks runs attacker-chosen shell commands, at runtime. The same Elo source compiled to JavaScript, Python, or SQL is benign, so the bug also breaks the cross-target portability guarantee the rest of the compiler honours. ### Vulnerable sinks Two sinks exist in at commit : 1. **String-literal emitter — lines 180–184.** The emitter escapes backslash, double quote, and control characters, but not . Any sequence in an Elo string literal flows straight into the emitted Ruby source. 2. **Labelled subtype-constraint branch — lines 405–412.** The error message passed to is wrapped in a Ruby double-quoted string with no escape pass at all. Because the parser at accepts single-quoted Elo strings as constraint labels, a label such as from its character set, and one emission path (the subtype-constraint label branch) performed no escape pass at all.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • npm @enspiritversion unspecified
  • npm @enspirit/elo<= 1.0.0

How to fix CVE-2026-44266

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-44266. EPSS is 1.00%. Act only if a listed version of Elo Ruby backend has is installed.

Which versions are affected?

Compare what you have installed with <= 1.0.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-116; CWE-1336: Improper Neutralization of Special Elements Used in a Template Engine; CWE-94: Code Injection. EPSS 1.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Nov 3, 2026 · GitHub Advisory Database

    Detected

    ### Summary Elo's Ruby backend emits attacker-controlled text into Ruby double-quoted strings without escaping the character. Because begins Ruby's interpolation sequences — , , , — and any expression wrapped in may use backticks for shell execution, an Elo program that contains a crafted string literal or a labelled subtype constraint compiles to Ruby that evaluates attacker-chosen Ruby, and thro

Sources

  • CVE.orgVulnerability recordCVE-2026-44266

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-7w38-ggh5-v542

    Elo Ruby backend has Remote Code Execution via unescaped interpolation in emitted string literals and subtype-constraint labels

    github.com
  • GitLab Advisory DatabasePackage advisoryCVE-2026-44266

    Elo's Ruby backend emits attacker-controlled text into Ruby double-quoted strings without escaping the # character. Because # begins Ruby's interpolation sequences — #{expr}, #@ivar, #@@cvar, #$gvar — and any expression wrapped in #{&hellip;} may use backticks for shell execution, an Elo program that contains a crafted string literal or a labelled subtype constraint compiles to Ruby that evaluates

    advisories.gitlab.com

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitLab Advisory DatabaseNov 8, 2026
  • GitHub Advisory DatabaseNov 7, 2026
  • CVE.orgNov 4, 2026