# CVE-2026-119446: Session fixation in the CLI login flow allows an unauthenticated attacker to obtain a user's API token

Status: published. Published: 2026-11-10. Updated: 2026-11-10.

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.

## Remediation

- fix: 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. (source: CNA: EEF)
- workaround: 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: CNA: EEF)
- fix: The reporting source identifies this reference as a patch. Check the advisory for affected versions and supported release branches. (source: CNA: EEF) — https://github.com/nerves-hub/nerves_hub_web/commit/3131f1701194b581ab4b3e5e9d81194fc9c83508

## Affected products and versions

- nerves-hub / nerves_hub_web (nerves-hub/nerves-hub): ≥ 2.5.0; < 2.5.3 (affected, other). Source: CNA: EEF
- nerves-hub / nerves_hub_web (nerves_hub): ≥ 2.5.0; < 2.5.3 (affected, semver). Source: CNA: EEF
- nerves-hub / nerves_hub_web (nerves-hub/nerves_hub_web): ≥ e6bf11a812d7aa8b69d854ba8ef02d65516f5564; < 3131f1701194b581ab4b3e5e9d81194fc9c83508 (affected, git). Source: CNA: EEF

## Severity and prioritization

- CVSS 4.0: 9.4 (critical); CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H; source: CNA: EEF

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-384

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-9vr9-463q-46qp (CNA: EEF; vendor-advisory, related)

- https://cna.erlef.org/cves/CVE-2026-119446.html (CNA: EEF; related)

- https://osv.dev/vulnerability/EEF-CVE-2026-119446 (CNA: EEF; related)

- https://github.com/nerves-hub/nerves_hub_web/commit/e6bf11a812d7aa8b69d854ba8ef02d65516f5564 (CNA: EEF; related)

- https://github.com/nerves-hub/nerves_hub_web/commit/3131f1701194b581ab4b3e5e9d81194fc9c83508 (CNA: EEF; patch)

## Provenance

- CNA: EEF: https://www.cve.org/CVERecord?id=CVE-2026-119446; retrieved 2026-11-10; source updated 2026-11-10

Revision: 833d31f4ebddbdeb247e4bf8345e19667d835e68c9eec7bec478464da76a4382

Canonical: https://y2.dev/cve/CVE-2026-119446

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.