CVE-2026-44267: enspirit elo · Cross-site Scripting
Affects enspirit eloSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical : upgrade to 1.0.1 as a priority.
Data as of 3 Nov 2026, 18:14 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 9.8 |
|---|
- Patch
- Available – fixed in 1.0.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade elo and enspirit/elo to 1.0.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| enspiritelo | Affected
| Fixed in
|
GitHubenspirit/elopkg:github/enspirit/eloOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to Elo version 1.0.1 or later, where this vulnerability is fixed. No other mitigation is required as the fix addresses the root cause by rejecting meta-properties and properly handling the 'constructor' identifier.
Description
CVE-2026-44267 is a critical cross-site scripting (XSS) vulnerability in the Elo expression language used by enspirit. Versions prior to 1.0.1 allow attacker-controlled strings to execute arbitrary JavaScript code via the .constructor.constructor property. This flaw affects the defaultFormats.elo.parse() function, the bin/elo CLI, and the elo-lang.org/try playground, enabling browser script execution and session compromise. It also permits arbitrary Node.js code execution in environments using the library. The issue is fixed in version 1.0.1.