ZDF
Sign inSign up

Vulnerabilities

Security fix · CVE-2026-44265

Elo backends have code injection via unvalidated emission of programmatic AST fields

Published Nov 3, 2026 · catalog updated Nov 3, 2026 · Elo backends have code

Last checked Nov 7, 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-44265. EPSS is 0.24%. Act only if a listed version of Elo backends have code 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 backends have code).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High7.4
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.24%
Remediation
Version ranges on file
Affected products
npm @enspirit · npm @enspirit/elo

### Summary Elo's programmatic AST API accepts arbitrary values in many node fields without runtime type or syntax validation. Each backend's emit stage interpolates those values straight into the generated source with no escape pass. An integrator that populates the AST from JSON-deserialised input, plugin output, or any other untyped source therefore exposes a code-injection primitive that flows through to the emitted JavaScript, Ruby, Python, or SQL. The same pattern was previously addressed in **0.9.7 (2026-01-27)**, which patched the date/datetime/duration literal emitters via after a report by **naoyashiga**. This advisory generalises that fix to the remaining AST surface — at least 23 emission sites across six node-field categories and four backends. ### Vulnerable sinks Each row is a category of sinks that share the same shape: TypeScript signature erased at runtime → AST-API consumer passes a crafted value → emit interpolates the value verbatim. | # | AST field | Affected backends | Resulting injection | |---|---|---|---| | 1 | / | JS, Ruby, Python, SQL | Arbitrary expression in the emitted numeric position (RCE on JS/Ruby/Python; SQL expression injection) | | 2 | | JS, Ruby, Python, SQL | Identifier-position injection; on SQL, raw SQL injection because undefined identifiers are intentionally emitted as column references | | 3 | | JS, Ruby, Python, SQL | Property access escaped into expression (RCE) | | 4 | key | JS, Ruby, SQL | Computed-key / extra-property injection (RCE on JS/Ruby; SQL injection) | | 5 | segment | JS, Ruby, Python, SQL | Ruby symbol-list injection allows backtick shell exec; SQL string-segment unquoted in single-quote context allows SQL injection | | 6 | | JS, Ruby, Python | Parameter-list structural injection (RCE) | | 7 | SQL binding | SQL | Identifier injection in clause | ### Proof of Concept End-to-end execution was verified at commit for representative cases per backend. Examples: **Numeric literal injection (all four backends).**

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-44265

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-44265. EPSS is 0.24%. Act only if a listed version of Elo backends have code 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-20: Improper Input Validation; CWE-749; CWE-89: SQL Injection. EPSS 0.24%. 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 programmatic AST API accepts arbitrary values in many node fields without runtime type or syntax validation. Each backend's emit stage interpolates those values straight into the generated source with no escape pass. An integrator that populates the AST from JSON-deserialised input, plugin output, or any other untyped source therefore exposes a code-injection primitive that flows

Sources

  • CVE.orgVulnerability recordCVE-2026-44265

    Official CVE identifier

    cve.org
  • GitHub Advisory DatabasePackage advisoryGHSA-x9rp-7wh3-2rj5

    Elo backends have code injection via unvalidated emission of programmatic AST fields

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

    Elo's programmatic AST API accepts arbitrary values in many node fields without runtime type or syntax validation. Each backend's emit stage interpolates those values straight into the generated source with no escape pass. An integrator that populates the AST from JSON-deserialised input, plugin output, or any other untyped source therefore exposes a code-injection primitive that flows through to

    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 7, 2026
  • GitHub Advisory DatabaseNov 7, 2026
  • CVE.orgNov 4, 2026