Mass assignment of organization, product and deployment group IDs allows users to write into other organizations and receive their firmware
Affects nerves_hub_web releases 1.0.0 through 2.5.2. Fixed in 2.5.3. No vendor rating is given, so the CVSS score of 8.6 (high) is the only severity listed.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected nerves_hub_web releases from 1.0.0 through 2.5.2 (fixed in 2.5.3).
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 17/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
nerves_hub's web interface and device API let a logged-in user write into other organizations by submitting modified organization, product, or deployment group IDs, so the attacker's devices receive those organizations' firmware. Because any account can be created, an attacker can reach this remotely over the network with low-privilege login and no user action.
Read the original description
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.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected nerves_hub_web releases from 1.0.0 through 2.5.2 (fixed in 2.5.3).Upgrade to a fixed version: 2.5.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120730 (Mass assignment of organization, product and deployment group IDs allows users to write into other organizations and receive their firmware), 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-120730 (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. Conditions (all must be true for the bug to be hit): - Affected nerves_hub_web releases from 1.0.0 through 2.5.2 (fixed in 2.5.3). (source: https://github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-rpp7-x9hm-jrmr) Setup: the bug is reachable in a default setup; no special feature or setting is needed. Attacker needs: network access, low-privilege login, no user action. CISA KEV: CVE-2026-120730 is not listed as of cve.now's last read. This KEV status is for CVE-2026-120730 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-rpp7-x9hm-jrmr - https://github.com/nerves-hub/nerves_hub_web/commit/c367d7d17d07f843e78a70d15904665616dde964 - https://cna.erlef.org/cves/CVE-2026-120730.html - https://osv.dev/vulnerability/EEF-CVE-2026-120730 - https://github.com/nerves-hub/nerves_hub_web/commit/f58d58233dbd355c58d3a140107ece18e8863f14 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-120730 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-120730.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- 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
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120730
Is CVE-2026-120730 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: cve.now feed data
What does this mean?
The web application accepts organization, product and deployment group IDs from the user's own request, so a user can attach a device to another organization's deployment group. The advisory says the deployment then sends that organization's current release with a download URL, and that devices, signing keys and products can be moved into another organization.Source: github.com
Which versions are affected by CVE-2026-120730?
nerves-hub/nerves-hub: from 1.0.0 before 2.5.3. nerves_hub: from 1.0.0 before 2.5.3.Source: cve.now feed data
Am I affected, and how do I check?
Releases of nerves_hub_web from 1.0.0 through 2.5.2 are affected. To check a deployment, look up which nerves_hub_web release it runs, and treat any release in that range as affected.Source: github.com
How do I fix CVE-2026-120730?
Upgrade nerves_hub_web to 2.5.3, the release that fixes this issue.Source: github.com