EnergizeLab vulnerabilities
We track 9 vulnerabilities in EnergizeLab products across 7 products. 9 are rated high or critical, and none are known to be exploited. The most recent was published on October 15, 2026.
Latest EnergizeLab vulnerabilities
- 8.8 High severity
NestJS auth service: Authorization Bypass Through User-Controlled Key
The EnergizeLab Eilik NestJS auth service accepts a user-controlled user ID in account update requests (mass assignment). A registered user can set another account's identifier and take over that account.
- 9.6 Critical severity
station-middleware: Missing Authorization
EnergizeLab station-middleware (NestJS) Docker images 1.6.5 through 1.8.2 do not check user roles on administrative APIs. Any authenticated low-privilege user can retrieve AI provider keys and change configuration and object-store contents.
- 9.8 Critical severity
FastAPI AI inference server: Missing Authentication for Critical Functionality
The EnergizeLab Eilik and EilikO FastAPI AI inference and profiling services expose AI model administration functions without authentication. An unauthenticated remote attacker can change AI model configuration and switch the model in use at runtime.
- 9.9 Critical severity
station-middleware: External Control of File Name or Path
EnergizeLab station-middleware (NestJS) Docker images 1.6.5 through 1.8.2 allow any registered, low-privilege account to read arbitrary files from the server by supplying an attacker-controlled file path. This exposes middleware files and server secrets.
- 7.5 High severity
Robot firmware (mode 104000): Download of Code Without Integrity Check
EnergizeLab AI Station firmware, EilikO Linux robot firmware v2.1_20260617182218_release, and the EnergizeLab Windows desktop app 3.1.2 download firmware updates over plain HTTP and do not verify their integrity or authenticity. An attacker able to intercept o
- 7.8 High severity
FirmwareUpdater: Use of Hard-coded Cryptographic Key
The EnergizeLab FirmwareUpdater (AArch64 ELF, distributed in the CDN bin.zip) uses a single hard-coded AES key shared by all installations. An attacker who recovers the key from the updater can decrypt and forge firmware packages for any device that trusts it.
- 8.2 High severity
NestJS auth service: Improper Authentication
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
- 8.8 High severity
AI Station firmware (RK3562): Use of Hard-coded Credentials
The EnergizeLab AI Station (RK3562) firmware image ships with default root credentials and SSH enabled. An attacker with network access to the device can log in as root and take full control of it.
- 9.1 Critical severity
FastAPI AI inference server: Improper Limitation of a Pathname to a Restricted Directory
The EnergizeLab Eilik and EilikO AI skill upload endpoint, served by the FastAPI AI inference and profiling services, does not require authentication and does not constrain uploaded file paths. An unauthenticated remote attacker can use path traversal to write