{"answers":{"affected":"2 open source packages ship an affected version, including nerves-hub/nerves-hub and nerves_hub. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120730 exists.","exposure":"","fix":"Upgrade nerves-hub/nerves-hub to 2.5.3 or later.","what":"CVE-2026-120730 is a high-severity vulnerability in nerves-hub nerves_hub_web, published on 10 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120730 and fix it if it is affected.\n\nWhat it is: CVE-2026-120730 is a high-severity vulnerability in nerves-hub nerves_hub_web, published on 10 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120730 exists.\n\nAffected packages and fixed versions:\n- nerves-hub/nerves-hub (oci): affected from 1.0.0; fixed in 2.5.3\n- nerves_hub (otp): affected from 1.0.0; fixed in 2.5.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-120730/ (Markdown: https://insights.sbomify.com/CVE-2026-120730/index.md)","id":"CVE-2026-120730","markdown":"https://insights.sbomify.com/CVE-2026-120730/index.md","name":"CVE-2026-120730","record":{"aliases":["EEF-CVE-2026-120730","GHSA-rpp7-x9hm-jrmr"],"analysis":null,"analysis_generated_by":null,"assigner":"EEF","cpe":[{"criteria":[{"cpe":"cpe:2.3:a:nerves-hub:nerves_hub_web:*:*:*:*:*:*:*:*","source":"cna","version_end_excluding":"2.5.3","version_start_including":"1.0.0"}],"n_criteria":1,"name":null,"product":"nerves_hub_web","vendor":"nerves-hub"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-915","name":"Improperly Controlled Modification of Dynamically-Determined Object Attributes"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.\n\nA 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.\n\nThis issue affects nerves_hub: from 1.0.0 before 2.5.3.","ecosystems":["oci","otp"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in the device API, device forms, signing key an","id":"CVE-2026-120730","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":5,"n_vendor_status":0,"next":{"headline":"Cleartext storage of sensitive information in the user account data in Devolutions Server 2026.3.12.0 and earlier allows an attacker with re","id":"CVE-2026-120733"},"nickname":null,"packages":[{"ecosystem":"oci","fixed":["2.5.3"],"introduced":["1.0.0"],"last_affected":[],"name_kind":null,"package":"nerves-hub/nerves-hub","purl":"pkg:oci/nerves-hub?repository_url=ghcr.io/nerves-hub/nerves-hub","purl_source":"cna","scope":"upstream","source":"CVE-2026-120730"},{"ecosystem":"otp","fixed":["2.5.3"],"introduced":["1.0.0"],"last_affected":[],"name_kind":null,"package":"nerves_hub","purl":"pkg:otp/nerves_hub?repository_url=https://github.com/nerves-hub/nerves_hub_web","purl_source":"cna","scope":"upstream","source":"CVE-2026-120730"}],"prev":{"headline":"Gitea stored cross-site scripting in the issue reference popup","id":"CVE-2026-120729"},"products":["nerves_hub_web"],"published":"2026-11-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-11-12","vendor_status":[],"vendors":["nerves-hub"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-120730/"}