EnergizeLab Eilik Unauthenticated Device-Token Issuance for Arbitrary Serial Numbers

published 2026-10-15 25d ago modified 2026-10-16 24d ago also EUVD-2026-102430

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits: 0; none known

The EnergizeLab Eilik NestJS auth service issues device tokens for arbitrary robot serial numbers without authentication. An unauthenticated remote attacker can obtain a valid device token for any serial number and act as that device against the cloud services.

Is CVE-2026-105034 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 24d ago (2026-10-16)

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N

Affected products

EnergizeLab NestJS auth service

Classification

Weakness

CWE-306 Missing Authentication for Critical Functionality
CWE-287 Improper Authentication

References

github.com /xn0tsa/your-secrets-are-safe-with-me
technical-description
takeonme.org /gcves/GCVE-1337-2026-0000000000000000000111111111110000000000000000000000001111111100111111111100000000000000
third-party-advisory
theverge.com /tech/1010727/eiliko-robot-hack-energize-lab
media-coverage

Sources

CVE List CVE-2026-105034
NVD CVE-2026-105034

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.