EM-20261103-Q5WN
VulnerabilityCritical severity
Critical Elo Vulnerability (CVE-2026-44267)
CVE-2026-44267
Status
Developing
Since : signals keep joining.
- First Signal
- Nov 03 17:53 UTCC26 GitHub Advisory Database
- Page Born
- Nov 03 18:18 UTCsecond source joined
- Last Signal
- Nov 03 18:18 UTC23 hours before snapshot
- Sources
- 20 official · 2 research, news or crowd
- Open For
- 21 hoursso far
Life Of This Page
- 1BornA second, independent source names it.
- 2Developing · NowNew signals join; severity can move.
- 3ConfirmedNot yetCISA KEV lists it, or exploitation in the wild is reported.
- 4ResolvedNot yetPast the fix deadline and 14 days with no new signal.
- 5ArchivedNot yet30 days after resolved. Read only; the link keeps working. Reopens if it comes back.
The address and ID never change. A correction is logged, never overwritten. If two pages turn out to be one incident, the later one points to the earlier.
Vulnerability Lifecycle
- Disclosed: reachedNov 03 18:18 UTCC6 NVD published
- Scored: reachedNov 03 18:18 UTCCVSS 9.8 · EPSS 0.8%
- Exploited: not yetNot yetNo exploitation reported
- Advisories: not yetNot yetNone yet
- Vendor Response: not yetNot yetNone in sources yet
- Resolved: not yetNot yetAfter 14 quiet days
Timeline
Point at a mark to read it. Squares are signals, colored by severity; every one is also listed under Signals.
Signals
- CVE-2026-44267 (CVSS 9.8) (opens source in a new tab) Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, plain Elo strings supplied to defaultFormats.elo.parse(), bin/elo, or elo-lang.org/try can use .constructor.constructor to reach JavaScrip… Crit severityDatabaseC6 NVD CVE API 2.0
- GHSA-33r5-xmm8-v6x5 / CVE-2026-44267: Elo JavaScript emitter has sandbox escape to arbitrary Node.js / browser code execution via unfiltered `.constructor` member access (opens source in a new tab) npm:@enspirit/elo Crit severityDatabaseC26 GitHub Advisory Database