CVE-2026-105034

Deferred Deferred - Pending Action

Authentication Bypass in Eilik NestJS Auth Service

Publication date: 2026-10-15

Last updated on: 2026-10-16

Assigner: Austin Hackers Anonymous

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-15

Last Modified

2026-10-16

Generated

2026-10-19

AI Q&A

2026-10-16

EPSS Evaluated

2026-10-18

NVD

CVE-2026-105034

Affected Vendors & Products

Vendor	Product	Version / Range
EnergizeLab	NestJS	auth service 1.8.2

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-287	When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
CWE-306	The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

Executive Summary

The EnergizeLab Eilik NestJS auth service allows unauthenticated attackers to obtain valid device tokens for any robot serial number. This means an attacker can impersonate any device without needing credentials or authentication.

Detection Guidance

To detect this vulnerability, monitor network traffic for unauthenticated requests to the EnergizeLab NestJS auth service endpoint that issue device tokens without proper authentication. Check logs for unusual token generation requests with arbitrary robot serial numbers.

Impact Analysis

An attacker could gain unauthorized access to cloud services by impersonating legitimate devices. This may lead to data breaches, unauthorized control of devices, or disruption of services relying on the auth service.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Non-compliance may result in legal penalties and reputational damage.

Mitigation Strategies

Immediately restrict access to the EnergizeLab NestJS auth service to authenticated users only. Disable any endpoints or functions that issue device tokens without proper authentication. Review and update firewall rules to block unauthorized requests to the service.

Hi! I’m here to help you understand CVE-2026-105034. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70