Answer in brief
CVE-2026-120286 records a Medium severity (CVSS 5.3) vulnerability in Missing authorization in device and deployment group page events allows view-role members to change devices and deployment groups. The current sources do not mark it as known exploited. The current feed maps nerves-hub/nerves-hub/nerves-hub (generic), nerves-hub/nerves-hub/nerves_hub_web (generic), nerves-hub/nerves_hub_web (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps nerves-hub/nerves-hub/nerves-hub (generic), nerves-hub/nerves-hub/nerves_hub_web (generic), nerves-hub/nerves_hub_web (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| nerves-hub/nerves-hub/nerves-hubgeneric | >=1.0.0 <2.5.3 | 2.5.3 |
| nerves-hub/nerves-hub/nerves_hub_webgeneric | >=7b511764a468bb2c1f33945874faa86af2255c0c <34ea112472a460319c1e1dec8ad0ffc37df05ffe | 34ea112472a460319c1e1dec8ad0ffc37df05ffe |
| nerves-hub/nerves_hub_webgeneric | >=1.0.0 <2.5.3 | 2.5.3 |
Published upstream
Nov 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 10, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 10, 2026
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.
Quoted source text, attributed separately from HOL analysis.