NervesHub (Nerves project) NervesHub organization isolation Flaw CVE-2026-120730: Update Now
The short version: CVE-2026-120730 is a high-severity security flaw in NervesHub (Nerves project) NervesHub organization isolation. The National Vulnerability Database (NVD) has published it, and the score it lists is 8.6 out of 10. When FraudMeNot checked, CISA had not added CVE-2026-120730 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
CVE-2026-120730 lets a NervesHub user reach into organizations they do not belong to. NervesHub is the open-source device management server from the Nerves project, used to manage devices and deliver firmware to them through deployment groups. By editing a few hidden identifiers in requests, a user who manages devices in any organization could attach a device to another organization's deployment group and be sent that organization's firmware, or plant signing keys, products and devices inside it.
The maintainers fixed the issue in NervesHub 2.5.3, as one of six security fixes in that release. Their advisory, GHSA-rpp7-x9hm-jrmr, points out why the bar is low: "Any signed-in user can create an organization and is its admin, so this needs nothing more than an account."
What went wrong
Several API endpoints and dashboard forms accepted an organization, product or deployment group ID from the client and saved it as given. Each request checked that the user held the manage role, or admin for certificate-authority settings, but only in the user's own organization. In the advisory's words: "Nothing checks the submitted IDs against it."
This class of bug is usually called mass assignment. The CVE record classifies it as CWE-915, improperly controlled modification of dynamically-determined object attributes, and the advisory also lists CWE-639, authorization bypass through a user-controlled key.
What an attacker could do
The advisory lists the affected requests and their effects:
- Device API update and the device settings form could move a device into another organization's product or onto its deployment group.
- Device API create and the new device form could create a device directly on another organization's deployment group.
- The new signing key form could add a firmware signing key to another organization.
- The new product form could add a product to another organization, and before 2.3.0 a product update could move a product into one.
- Certificate-authority JITP settings could point automatic device provisioning at another organization's product.
The most direct consequence is firmware exposure. The advisory states that "a device attached this way is sent the other organization's firmware." The CVSS vector the CVE record publishes rates confidentiality and integrity impact as high and availability as unaffected, which matches reading firmware and altering another organization's records rather than taking the service down.
Who is affected
Every release from 1.0.0 through 2.5.2 is affected, including the container image ghcr.io/nerves-hub/nerves-hub. The device create paths have been affected since 2.0.0 and the other requests since 1.0.0. The fix is in 2.5.3, commit c367d7d.
Exposure is wider where more people can get accounts. The advisory notes that leaving open registration off "limits this to people with an account, but any account can create an organization," and that with Google sign-in enabled, anyone with a Google account could get one before 2.5.3, a separate flaw fixed in the same release.
Severity and who scored it
The Erlang Ecosystem Foundation (EEF), the CVE Numbering Authority for the Erlang and Elixir ecosystem, assigned the CVE and scored it CVSS 4.0 8.6 High, vector AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N. That means a network attack of low complexity by a logged-in, low-privilege user, with no help from anyone else. NVD lists the score as secondary and had not added its own assessment when FraudMeNot checked. There is no CVSS 3.1 score. The record credits Josh Kalderimis as finder, reporter and remediation developer, and Jonatan Männchen of the EEF as coordinator. CISA had not listed the CVE as exploited.
What 2.5.3 changes
The device API and dashboard device forms now save only the fields a client may set, and ignore organization, product and deployment IDs. Signing-key and product forms take the organization from the session. A JITP product must belong to the certificate authority's organization. When a device connects, NervesHub now takes it off any deployment group of another product, even if that group's membership is locked, and refuses a device whose organization does not own its product. An upgrade migration removes existing cross-product deployment memberships and logs each change.
Timeline
- NervesHub 2.5.3 is released, the maintainers publish GHSA-rpp7-x9hm-jrmr, and EEF publishes the CVE record.
What to do
These steps are for administrators who run a NervesHub server and for the owners of each organization on it.
- Upgrade to 2.5.3 or later. The advisory says there is no configuration workaround. Read the release's "Upgrading" section first: the migration can take devices off deployment groups, and devices whose organization does not own their product will be refused when they connect until their
product_idis corrected or they are deleted. - Check the database before upgrading. The advisory publishes SQL queries that find devices sitting on another product's deployment group. Running them first shows which devices the migration will move.
- Look for leftovers after upgrading. "Upgrading doesn't undo anything else done this way," the maintainers warn. Use their queries to find devices whose organization does not own their product, signing keys created by someone who was never a member of the organization, and certificate authorities whose provisioning product belongs to another organization. Remove anything that should not be there.
- Review what you own. A device moved wholly into another organization, or a product added to one, "leave nothing that sets them apart," so organization owners should review their devices, products and signing keys for entries they do not recognise.
- Consider who can sign up. Limiting registrations reduces how many people could have tried this, though it does not replace the upgrade.
What the official record says about CVE-2026-120730
The record was filed by 6b3ad84c-e1a6-4bf7-a703-f496b71e49db. In its own words: "Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in the device API, device forms, signing key and product forms and JITP settings in nerves-hub nerves_hub_web allows an authenticated user who manages devices in any organization to write into other organizations via submitted org_id, product_id and deployment_id fields. The device API create and update actions and the dashboard device forms pass the request parameters to NervesHub.Devices.Device.changeset/2, which casts the organization, product, deployment group and update state as given. The signing key and product forms merge the session's organization into the submitted parameters so that a submitted org_id wins, and the JITP changeset accepts any product_id. Each request requires the manage role only in the user's own organization, and any account can create one. A device placed on another organization's deployment group, or moved into its product, is sent that organization's firmware with a download URL. The user cannot change or control devices that already belong to the other organization, and cannot upload firmware to it. This issue affects nerves_hub: from 1.0.0 before 2.5.3."
Why NervesHub organization isolation admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). 6b3ad84c-e1a6-4bf7-a703-f496b71e49db rated CVE-2026-120730 8.6 (High) under CVSS 4.0. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping NervesHub organization isolation running is none. Scoring string: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X.
Affected NervesHub organization isolation releases
According to the record, these releases are vulnerable:
- 1.0.0 up to, but not including, 2.5.3
- 1.0.0 up to, but not including, 2.5.3
- f58d58233dbd355c58d3a140107ece18e8863f14 up to, but not including, c367d7d17d07f843e78a70d15904665616dde964
The type of bug behind CVE-2026-120730
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-639, Authorization Bypass Through User-Controlled Key. MITRE describes this class of bug as follows: "The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data."
- CWE-915, Improperly Controlled Modification of Dynamically-Determined Object Attributes. MITRE describes this class of bug as follows: "The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified."
Vendor remediation for CVE-2026-120730
The vendor advisory remediation for operators of NervesHub organization isolation, quoted for this page, is: "Patch: upgrade nerves_hub_web / ghcr.io/nerves-hub/nerves-hub from 1.0.0-2.5.2 to 2.5.3 or later (commit c367d7d). No configuration workaround (maintainer advisory). Read the 2.5.3 Upgrading notes: the migration removes cross-product deployment memberships and devices whose org does not own their product are refused until fixed. Run the advisory's SQL checks before and after upgrading; review devices, products and signing keys for unknown entries. Who acts: NervesHub server administrators and organization owners. Score: EEF (CNA) CVSS 4.0 8.6 High (NVD Secondary). Not in CISA KEV when checked."
What to do about it
- Update now: Patch: upgrade nerves_hub_web / ghcr.io/nerves-hub/nerves-hub from 1.0.0-2.5.2 to 2.5.3 or later (commit c367d7d). No configuration workaround (maintainer advisory). Read the 2.5.3 Upgrading notes: the migration removes cross-product deployment memberships and devices whose org does not own their product are refused until fixed. Run the advisory's SQL checks before and after upgrading; review devices, products and signing keys for unknown entries. Who acts: NervesHub server administrators and organization owners. Score: EEF (CNA) CVSS 4.0 8.6 High (NVD Secondary). Not in CISA KEV when checked.
- Who should act: IT teams, managed service providers, and developers who run or ship NervesHub organization isolation. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from NervesHub (Nerves project) (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from the patch release onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-120730. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-120730 record details from CISA and NVD
- Attack complexity for CVE-2026-120730: low
- CVE-2026-120730 attack requirements: none
- Impact on connected systems: secrecy none, integrity none, availability none.
- Who mapped the weakness type: 6b3ad84c-e1a6-4bf7-a703-f496b71e49db (Secondary)
- References in the NVD record: 5.
What the official record shows
- NVD has published CVE-2026-120730.
- When FraudMeNot checked the CISA KEV catalog, CVE-2026-120730 was not listed.
- The NVD record status is Received.
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- cna.erlef.org/cves/CVE-2026-120730.html
- github.com/nerves-hub/nerves_hub_web/commit/c367d7d17d07f843e78a70d15904665616dde964
- github.com/nerves-hub/nerves_hub_web/commit/f58d58233dbd355c58d3a140107ece18e8863f14
- github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-rpp7-x9hm-jrmr
- osv.dev/vulnerability/EEF-CVE-2026-120730
Sources
- NVD: CVE-2026-120730
- CVE.org: CVE-2026-120730
- NervesHub (Nerves project) advisory
- NervesHub (Nerves project) advisory
- NervesHub (Nerves project) advisory
- MITRE CWE-639
- MITRE CWE-915
General education only, not security advice. Facts checked against the sources above.