EM-20261103-NK9I VulnerabilityHigh severity

Elo Vulnerability (CVE-2026-44265)

CVE-2026-44265

Status

Developing

Since Nov 03 18:18 UTC: signals keep joining.

First Signal: Nov 03 17:48 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

1
Born

Nov 03 18:18 UTC
A second, independent source names it.
2
Developing · Now

Nov 03 18:18 UTC
New signals join; severity can move.
3
Confirmed

Not yet
CISA KEV lists it, or exploitation in the wild is reported.
4
Resolved

Not yet
Past the fix deadline and 14 days with no new signal.
5
Archived

Not yet
30 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: reached

Nov 03 18:18 UTC
C6 NVD published
Scored: reached

Nov 03 18:18 UTC
CVSS 7.4 · EPSS 0.2%
Exploited: not yet

Not yet
No exploitation reported
Advisories: not yet

Not yet
None yet
Vendor Response: not yet

Not yet
None in sources yet
Resolved: not yet

Not yet
After 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

Nov 03 18:18 UTCCVE-2026-44265 (CVSS 7.4) (opens source in a new tab) Elo is a purely functional expression language for no-code tools. Prior to 1.0.1, Elo's programmatic AST API accepts arbitrary values from JSON-deserialized input, plugin output, or other untyped sources and interpolates… High severityDatabaseC6 NVD CVE API 2.0
Nov 03 17:48 UTCGHSA-x9rp-7wh3-2rj5 / CVE-2026-44265: Elo backends have code injection via unvalidated emission of programmatic AST fields (opens source in a new tab) npm:@enspirit/elo High severityDatabaseC26 GitHub Advisory Database