{"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-120999 exists.","exposure":"","fix":"Upgrade nerves-hub/nerves-hub to 2.5.3 or later.","what":"CVE-2026-120999 is a high-severity vulnerability in nerves-hub nerves_hub_web, published on 10 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-120999 and fix it if it is affected.\n\nWhat it is: CVE-2026-120999 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-120999 exists.\n\nAffected packages and fixed versions:\n- nerves-hub/nerves-hub (oci): affected from 2.3.0; fixed in 2.5.3\n- nerves_hub (otp): affected from 2.3.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-120999/ (Markdown: https://insights.sbomify.com/CVE-2026-120999/index.md)","id":"CVE-2026-120999","markdown":"https://insights.sbomify.com/CVE-2026-120999/index.md","name":"CVE-2026-120999","record":{"aliases":["EEF-CVE-2026-120999","GHSA-r92p-gg92-gmwm"],"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":"2.3.0"}],"n_criteria":1,"name":null,"product":"nerves_hub_web","vendor":"nerves-hub"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Improper Authentication vulnerability in Google sign-in and email confirmation in nerves-hub nerves_hub_web allows an attacker who registers another person's email address to share that person's account once they sign in. NervesHub.Accounts.update_or_create_user_from_ueberauth/1 signs a Google user in to any account carrying the same email that is not yet linked to a Google account, links it and marks the email confirmed, without the account's owner ever having proved they own the address. NervesHubWeb.SessionController.confirm/2 likewise signs in whoever follows a confirmation link. An attacker registers the address from the sign-up form, changes their own account's email to it, or registers it as an organization admin from an invite link, and keeps the password; when the address's owner signs in with Google or follows the confirmation link, they land in that account.\n\nThe Google path also creates accounts with registrations closed and never checks Google's email_verified claim, and the API's password sign-in in NervesHubWeb.API.UserController issues tokens to accounts whose email was never confirmed. The attacker gains only what the victim is granted afterwards, and nothing on accounts whose owners never use either path.\n\nThis issue affects nerves_hub: from 2.3.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":"Improper Authentication vulnerability in Google sign-in and email confirmation in nerves-hub nerves_hub_web allows an attacker who registers","id":"CVE-2026-120999","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":"HTTP::Body versions before 1.24_02 for Perl parse the trailer in quadratic time","id":"CVE-2026-121006"},"nickname":null,"packages":[{"ecosystem":"oci","fixed":["2.5.3"],"introduced":["2.3.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-120999"},{"ecosystem":"otp","fixed":["2.5.3"],"introduced":["2.3.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-120999"}],"prev":{"headline":"Improper Session Invalidation vulnerability in the dashboard pages, device console and local shell channels in nerves-hub nerves_hub_web all","id":"CVE-2026-120997"},"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-120999/"}