nerves_hub_web: Improper Authorization
CVE-2026-28806 is a high-severity improper authorization vulnerability in nerves_hub_web from Nerves-hub, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 2.4.0, 1f69c9d595684a4650c3ac702f3dc7c5bcd7526c as the first without the flaw, so updating nerves_hub_web to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.48% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update nerves_hub_web to 2.4.0 or 1f69c9d595684a4650c3ac702f3dc7c5bcd7526c, whichever matches your release line, or a later version.
- Update Nerveshub to 2.4.0 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Nerves-hub | nerves_hub_web | 1.0.0 up to, but not including, 2.4.0; adaeefdb7a835525482588f43332ef988cc448c7 and later; 79743ef08f7f801617b653fd09f37c01ed9b4be0 up to, but not including, 1f69c9d595684a4650c3ac702f3dc7c5bcd7526c | 2.4.0, 1f69c9d595684a4650c3ac702f3dc7c5bcd7526c |
| Nerves-hub | Nerveshub | 1.0.0 up to, but not including, 2.4.0 | 2.4.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 9.4 | Critical | CNA |
| CVSS 3.1 | 8.8 | High | NVD |
Official description
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: from 1.0.0 before 2.4.0.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authorization
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that you perform access control checks related to your business logic. These checks may be different than the access control checks that you apply to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- cna.erlef.org/cves/CVE-2026-28806.htmlThird Party Advisory
- github.com/nerves-hub/nerves_hub_web/commit/1f69c9d595684a4650c3ac702f3dc7c5bcd7526c
- github.com/nerves-hub/nerves_hub_web/commit/79743ef08f7f801617b653fd09f37c01ed9b4be0
- github.com/nerves-hub/nerves_hub_web/commit/adaeefdb7a835525482588f43332ef988cc448c7
- osv.dev/vulnerability/EEF-CVE-2026-28806Third Party Advisory
Other vulnerabilities in nerves_hub_web
- 7.4 High severity
- 8.6 High severity
- 7.1 High severity
- 9.4 Critical severity
- 9.8 Critical severity
Recent Improper Authorization vulnerabilities
- 9.9 Critical severity
- 7.5 High severity
- 9.4 Critical severity
- 9.8 Critical severity
- 7.7 High severity
- 8.8 High severity
Spotted an error? Tell us.