# CVE-2026-120999: Improper Authentication vulnerability in Google sign-in and email confirmation in nerves-hub nerves_hub_web allows an attacker who registers


- **Severity:** High 7.4 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** EEF-CVE-2026-120999, GHSA-r92p-gg92-gmwm

## What is CVE-2026-120999?

CVE-2026-120999 is a high-severity vulnerability in nerves-hub nerves_hub_web, published on 10 Nov 2026. 

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

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.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-120999?

2 open source packages ship an affected version, including nerves-hub/nerves-hub and nerves_hub. It affects 1 product.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `nerves-hub/nerves-hub` | oci | `pkg:oci/nerves-hub?repository_url=ghcr.io/nerves-hub/nerves-hub` | From 2.3.0 | 2.5.3 |
| `nerves_hub` | otp | `pkg:otp/nerves_hub?repository_url=https://github.com/nerves-hub/nerves_hub_web` | From 2.3.0 | 2.5.3 |

Products: Nerves-Hub Nerves Hub Web.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:nerves-hub:nerves_hub_web:*:*:*:*:*:*:*:*` from 2.3.0 before 2.5.3

## How do I fix CVE-2026-120999?

Upgrade nerves-hub/nerves-hub to 2.5.3 or later.

## Is CVE-2026-120999 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120999 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120999 and fix it if it is affected.

What it is: CVE-2026-120999 is a high-severity vulnerability in nerves-hub nerves_hub_web, published on 10 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120999 exists.

Affected packages and fixed versions:
- nerves-hub/nerves-hub (oci): affected from 2.3.0; fixed in 2.5.3
- nerves_hub (otp): affected from 2.3.0; fixed in 2.5.3

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120999/ (Markdown: https://insights.sbomify.com/CVE-2026-120999/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120999
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120999
- OSV: https://osv.dev/vulnerability/CVE-2026-120999

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120999/
Summaries are generated and may contain mistakes; the official description above is the record.
