External risk intelligence

EnergizeLab Station-Middleware Role Check Bypass Allows Unauthorized Access to Keys and Configuration.

CVE advisorySeverity: CRITICAL (CVSS 9.6)

CVE-2026-105039

The product is a middleware service implemented in NestJS, which is commonly used for web applications and API services. As an administrative API interface for station middleware, it is typically deployed as a network-accessible service to facilitate management and configuration, making it likely to be reachable in many real-world deployments.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in EnergizeLab station-middleware where authenticated users with low privileges can access sensitive AI provider keys and alter system configurations and data stores due to a lack of role checks on administrative APIs. The main concern is confirming relevance and exposure.

  • Low-privilege users can access keys and change settings.
  • Matters if administrative APIs are used with sensitive data.
  • Confirm if your system has this vulnerable middleware.

Attack Path

How an attacker could exploit the issue

An attacker with existing authenticated access to the system can leverage the lack of proper role checks on administrative APIs to gain elevated privileges. By targeting these APIs, the attacker can access sensitive information like AI provider keys and modify critical system settings or data, potentially leading to a complete compromise of the EnergizeLab station-middleware.

  • Authenticated low-privilege user access is required.
  • Administrative APIs do not check user roles.
  • Sensitive data exposure and configuration changes.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, authenticated low-privilege users could access administrative APIs to retrieve AI provider keys and alter configuration and object-store contents.

  • AI provider keys and configuration data at risk.
  • Access administrative APIs without proper authorization.
  • Unauthorized modification of system settings and data.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in EnergizeLab station-middleware impacts administrative APIs, potentially allowing authenticated low-privilege users to access sensitive information and modify system configurations. Responsibility likely falls to the platform or application teams managing the middleware, in coordination with security teams for exposure assessment. The first practical move is to identify all deployments of the affected middleware, confirm their network reachability and business criticality, and then assign an accountable owner to plan remediation based on this risk assessment.

  • Platform or application teams own the issue.
  • Verify affected middleware deployments and reachability.
  • Plan remediation based on risk and business criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is EnergizeLab station-middleware?

EnergizeLab station-middleware is a backend software component built on the NestJS framework. It acts as a central communication hub, managing administrative tasks, configuration settings, and object storage for connected systems. It is primarily used to facilitate the orchestration and management of AI provider integrations and system-wide data operations.

How does CVE-2026-105039 work?

This vulnerability is classified as CWE-862, which is a missing authorization flaw. In this case, the software fails to verify if a user has the appropriate administrative permissions before granting access to sensitive API endpoints. Because of this oversight, a low-privilege user can interact with functions intended only for administrators.

Do I need to be an admin to trigger this bug?

No, you do not need administrative privileges to trigger the vulnerability. You only need a standard, low-privilege account that is already authenticated to the system. However, the bug cannot be triggered by unauthenticated users or those completely outside the system; it requires existing access to reach the administrative API paths.

Why is my EnergizeLab setup potentially at risk?

Halo Surface Signal indicates that because this middleware serves as an administrative management interface, it is frequently deployed as a network-accessible service. If your specific instance is reachable over a network, authenticated users—even those with limited rights—may be able to bypass intended restrictions to access your AI keys or change configurations.

What should I do if I use this software?

First, conduct an inventory to identify all active deployments of the affected EnergizeLab station-middleware versions. Determine which of these instances are network-accessible and hold critical data. Once identified, assign a lead from your application or platform team to evaluate the risk and prioritize the implementation of updates or compensating security controls.

References