CVE-2026-120999 · Package
NO FIX YET · SEE WHAT TO DO
NervesHub's Google sign-in and email confirmation link accounts to an email address without proving the account owner controls it. An attacker who registers a victim's email first keeps access to the account and gets into it when the owner signs in with Google or follows the confirmation link.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Self-hosted NervesHub instances running version 2.3.0 through 2.5.2 that have Google sign-in or email confirmation in use. The attacker needs no existing account: they register the victim's address first. Deployments on versions 2.5.3 or later, or that do not use either path, are not exposed to the account-sharing flow.
Not affected if no-email-confirmation, no-google-sign-in, version-2.5.3-or-later
Who cares elixir, google-sign-in, nerves_hub, self-hosted
mix.lock; the affected range is 2.3.0 up to but not including 2.5.3.2.5.3 or laterImproper 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.
The 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.
This issue affects nerves_hub: from 2.3.0 before 2.5.3.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
This page as .md · .json · 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/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
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.