CVE-2026-119446
Critical 9.4No known exploitationFix availableSession fixation in the CLI login flow allows an unauthenticated attacker to obtain a user's API token
Record last updated
CVSS score
Critical on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
No EPSS score available
CISA remediation deadline
Not in the KEV catalog
Description
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/ 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.
Weakness: CWE-384
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Vendor solution
- Upgrading does not revoke tokens already handed out. A token from a CLI login is an ordinary API token with a note the client chose, so one an attacker obtained looks like any other. After upgrading, users should review their API tokens on the account page and delete any they do not recognise.
- Mitigation
- Block POST /api/auth/cli_session at the reverse proxy until the upgrade. It is the only entry point that creates a CLI login, so no link can be produced while it is blocked. CLIs can still sign in with an email and password (nh user auth, POST /api/users/auth), or use an API token created on the account page. Source (opens in a new tab)
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| nerves-hub | nerves_hub_web | from 2.5.0 before 2.5.3 | 2.5.3 | CVE Program |
| nerves-hub | nerves_hub_web | from 2.5.0 before 2.5.3 | 2.5.3 | CVE Program |
| nerves-hub | nerves_hub_web | from e6bf11a812d7aa8b69d854ba8ef02d65516f5564 before 3131f1701194b581ab4b3e5e9d81194fc9c83508 | 3131f1701194b581ab4b3e5e9d81194fc9c83508 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 3131f17 in nerves-hub/nerves_hub_web (opens in a new tab)patch
- CLI login links give an API token to whoever sent them (opens in a new tab)vendor-advisory, related
- EEF CNA record for CVE-2026-119446 (opens in a new tab)related
- Introducing commit e6bf11a in nerves-hub/nerves_hub_web (opens in a new tab)related
- OSV record EEF-CVE-2026-119446 (opens in a new tab)related