External risk intelligence

Session Fixation in NervesHub CLI Login Grants API Tokens via Crafted Links.

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-119446

The vulnerability affects a web-based service platform (nerves_hub_web) that facilitates device and session management. Such platforms are typically deployed as internet-facing web applications or API gateways to allow remote management and authentication of devices and users, making the web-based login and session handling interfaces commonly accessible via the public internet.

Cross-site Request Forgery

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

A session fixation vulnerability exists in the nerves-hub web interface, allowing an unauthenticated attacker to potentially gain API access to another user's account by tricking them into clicking a specially crafted login link. This could lead to unauthorized access and control over user accounts.

  • Unauthenticated access to user API tokens.
  • Confirms the need for diligent user link verification.
  • Assess relevance to your connected device infrastructure.

Attack Path

How an attacker could exploit the issue

An attacker can initiate a CLI login flow without any authentication to obtain a special link. By tricking a logged-in user into clicking this link and confirming the login, the attacker can then retrieve an API token associated with that user's account. This allows the attacker to impersonate the user and access their account details.

  • No authentication required initially.
  • User confirms malicious login link.
  • Attacker gains unauthorized API token.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated attacker could obtain an API token for another user's account by tricking that user into clicking a specially crafted login link. This could allow the attacker to impersonate the targeted user through their API token.

  • User API tokens could be exposed.
  • Attacker crafts a malicious login link.
  • Unauthorized account access may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

The nerves_hub_web platform, specifically its CLI login flow, is susceptible to session fixation, potentially allowing an unauthenticated attacker to obtain an API token. Owners of the nerves_hub_web application should first confirm its deployment and accessibility. The immediate practical next step involves identifying all instances of the affected technology, verifying its exposure and business criticality, and then coordinating remediation efforts with the accountable team, which is likely the application or platform owner.

  • Application owners should manage this issue.
  • Verify nerves_hub_web instances and accessibility.
  • Plan remediation based on risk.

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 nerves_hub_web and why is it used?

nerves_hub_web is a web component for NervesHub, an open-source platform designed to manage firmware updates and oversee the lifecycle of remote embedded devices. It provides the necessary interface for developers to authenticate, manage sessions, and coordinate software deployments across fleets of distributed devices.

What does CWE-384 Session Fixation mean for CVE-2026-119446?

This vulnerability, classified as CWE-384, means the authentication system fails to properly invalidate or rotate sessions during the login process. In this specific case, an attacker can pre-initialize a login session, trick an authenticated user into completing the confirmation steps, and hijack the resulting API token created for that user.

How does an attacker trigger this vulnerability?

An attacker starts by initiating a CLI login request to generate a session link. They must then deceive a currently logged-in user into visiting that specific link and clicking the confirmation button. The bug cannot be triggered automatically; it relies on the user performing the confirmation action, as the platform correctly prevents framed pages and uses CSRF protections.

Is my instance of nerves_hub_web at risk?

Halo Surface Signal indicates that platform components like nerves_hub_web are frequently deployed as internet-facing services to facilitate remote device management. If your interface is accessible via the public internet, it falls into the primary risk category for this type of externally triggered session manipulation.

How should I respond to this security notice?

Begin by auditing your environment to identify all instances of nerves_hub_web within your infrastructure. Once you have located these deployments, assess their network accessibility and business criticality. Coordinate with your application or platform ownership teams to prioritize remediation efforts for any systems running the affected versions.

References