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