# CVE-2026-119446: nerves_hub_web session fixation in CLI login

Source: https://junglewise.ai/threats/cve-2026-119446-session-fixation-vulnerability-in-the-cli-login-flow-in-nerves  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-10. Updated: 2026-11-10  
License: CC BY 4.0 with a link back

CVE-2026-119446 · Severity: info · Published 2026-11-10

NervesHub is a management platform for IoT devices running on the Nerves embedded Linux framework. A session fixation vulnerability in the CLI login flow allows an attacker to trick a signed-in user into clicking a malicious link, after which the attacker can steal an API token for that user's account. An attacker with an API token can perform actions on behalf of the compromised user, potentially gaining unauthorized access to managed IoT devices.

Technologies: [NervesHub Nerves Hub Web](https://junglewise.ai/threats/technologies/nerves-hub-web). Vendors: [NervesHub](https://junglewise.ai/threats/vendors/nerveshub).

## Quick answers

**Is CVE-2026-119446 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-119446 being exploited in the wild.

**How severe is CVE-2026-119446?** Informational severity, published 10 November 2026.

**Which products and versions are affected?** NervesHub Nerves Hub Web 2.5.0 before 2.5.3.

**Is there a fix for CVE-2026-119446?** Yes: fixed in nerves_hub_web 2.5.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-119446 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-119446?** Check whether you run NervesHub Nerves Hub Web at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in nerves_hub_web 2.5.3

## Technical details

The vulnerability exists in the CLI login flow where POST /api/auth/cli_session requires no authentication and returns a polling token and confirmation URL. When a signed-in user opens the attacker-controlled URL and clicks Confirm, NervesHub.Accounts.verify_cli_session_token/2 generates an API token for the user's account without verifying that the user who started the login is the one confirming it. The confirmation code is displayed but never validated, and although the form has CSRF protection and the page cannot be framed, social engineering can compel a user to open the link and click the button.

## Affected products

- NervesHub nerves_hub_web 2.5.0 before 2.5.3

## Timeline

- 2026-11-10: disclosed

## References

- [https://ghcr.io/](https://ghcr.io/)
- [https://github.com/](https://github.com/)

## Related threats

- [NervesHub improper authentication in sign-in and email confirmation](https://junglewise.ai/threats/cve-2026-120999-improper-authentication-vulnerability-in-google-sign-in-and)
- [NervesHub cross-organization data access via object attribute injection](https://junglewise.ai/threats/cve-2026-120730-improperly-controlled-modification-of-dynamically-determined)
- [NervesHub nerves_hub_web incorrect authorization in bulk move](https://junglewise.ai/threats/cve-2026-120295-incorrect-authorization-vulnerability-in-the-devices-page-bulk)