nerves-hub nerves_hub_web up to 2.5.2 Account Linking/Session Confirmation improper authentication

Summaryinfo

A vulnerability, which was classified as critical, has been found in nerves-hub nerves_hub_web up to 2.5.2. This vulnerability affects the function NervesHub.Accounts.update_or_create_user_from_ueberauth/NervesHubWeb.SessionController.confirm of the component Account Linking/Session Confirmation. Performing a manipulation results in improper authentication. This vulnerability was named CVE-2026-120999. The attack may be initiated remotely. There is no available exploit. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in nerves-hub nerves_hub_web up to 2.5.2. This affects the function NervesHub.Accounts.update_or_create_user_from_ueberauth/NervesHubWeb.SessionController.confirm of the component Account Linking/Session Confirmation. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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. 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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-120999 since 11/09/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

Upgrading to version 2.5.3 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• nerves-hub

Name

• nerves_hub_web

Version

• 2.5.0
• 2.5.1
• 2.5.2

Website

• Product: https://github.com/nerves-hub/nerves_hub_web/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion