CVE Catalog

CVE-2026-119446

CriticalCVSS 9.4
Published: Translated: NVD NIST

Summary

A Session Fixation vulnerability in the CLI login flow in nerves_hub_web allows an unauthenticated attacker to obtain an API token for another user's account via a crafted login link. The confirmation code is only displayed and never compared, so it cannot prove that the confirming person is the one who started the login.

Risk Assessment

An attacker can hijack a victim's API token if they persuade the user to open the link and click confirm, granting access to the victim's account. This requires user interaction but can lead to unauthorized access to device and firmware management.

Recommendation

Update nerves_hub to version 2.5.3 or later, which fixes this vulnerability. Additionally, inform users about the risks of opening unknown CLI login links.

Other vulnerabilities in nerves_hub_web

See all
Original NVD description (English source)

Session Fixation vulnerability in the CLI login flow in nerves-hub nerves_hub_web allows an unauthenticated attacker to obtain an API token for another user's account via a crafted login link. Starting a CLI login with POST /api/auth/cli_session needs no authentication and returns a polling token, a confirmation URL that carries that token, and a confirmation code. When a signed-in user opens that URL and clicks Confirm, NervesHub.Accounts.verify_cli_session_token/2 creates an API token for the user's account and stores it on the login, and the next poll of GET /api/auth/cli_session/<token> returns it to whoever started the login. The confirmation code is only displayed and is never compared with anything, so it cannot show that the person confirming is the one who started the login. The confirm form carries a CSRF token and the page cannot be framed, so the attacker has to persuade the user to open the link and click the button themselves. This issue affects nerves_hub: from 2.5.0 before 2.5.3.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS