CVE-2026-28806: Improper authorization in device bulk actions and device update API allows cross-organization device control
Improper Authorization vulnerability in nerves-hub nerves_hub_web allows cross-organization device control via device bulk actions and device update API.
Missing authorization checks in the device bulk actions and device update API endpoints allow authenticated users to target devices belonging to other organizations and perform actions outside of their privilege level.
An attacker can select devices outside of their organization by manipulating device identifiers and perform management actions on them, such as moving them to products they control. This may allow attackers to interfere with firmware updates, access device functionality exposed by the platform, or disrupt device connectivity.
In environments where additional features such as remote console access are enabled, this could lead to full compromise of affected devices.
This issue affects nerves_hub_web: from 1.0.0 before 2.4.0.
Security readout for executives and security teams
Plain-English summary
CVE-2026-28806 lets an authenticated NervesHub user control devices outside their organization through missing authorization checks. In a multi-tenant device-management environment, this can disrupt connectivity, interfere with firmware management, and, where remote console features are enabled, may contribute to full device compromise.
Executive priority
Treat this as urgent for any NervesHub environment managing production or customer devices. The issue can cross organizational boundaries and affect device integrity, availability, and confidentiality, so remediation should be prioritized ahead of routine maintenance.
Technical view
nerves_hub_web versions from 1.0.0 before 2.4.0 lack proper authorization in device bulk action and device update API endpoints. Authenticated users can manipulate device identifiers to target devices from other organizations and perform management actions beyond their privileges.
Likely exposure
Exposure is likely for self-hosted or managed NervesHub deployments running nerves_hub_web before 2.4.0, especially where multiple organizations share the platform or remote console capabilities are enabled.
Exploitation context
The source bundle does not show active exploitation or KEV listing. Exploitation requires authenticated access, but no user interaction and low complexity are reported. The business risk is cross-tenant device control rather than public unauthenticated takeover.
Researcher notes
Focus review on authorization boundaries in device bulk actions and device update handlers. Validate that device identifiers are constrained to the authenticated user’s organization before management actions execute. Do not assume exploitation beyond what the sources state.
Mitigation direction
Upgrade nerves_hub_web to version 2.4.0 or later.
Apply the referenced patch if maintaining a fork.
Review the GitHub advisory for vendor-specific deployment guidance.
Restrict management access while remediation is underway.
Validation and detection
Inventory nerves_hub_web deployments and versions.
Flag versions from 1.0.0 before 2.4.0 as affected.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-285: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-285 · source CWE mapping
Improper Authorization
Improper Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Exposure of Resource to Wrong Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.