# CVE-2026-1201: Authorization Bypass Through User-Controlled Key in Hubitat Elevation Hubs

> Remote authenticated users can control unauthorized devices via request manipulation, requiring an upgrade to secure home automation hubs.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** GHSA-gfwv-5762-mwrm

## What is CVE-2026-1201?

CVE-2026-1201 is a critical authentication bypass vulnerability in Hubitat Elevation C3, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An Authorization Bypass Through User-Controlled Key vulnerability in Hubitat Elevation home automation controllers prior to version 2.4.2.157 could allow a remote authenticated user to control connected devices outside of their authorized scope via client-side request manipulation.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

No fix has been published for CVE-2026-1201 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-1201 being exploited?

There is no known exploitation of CVE-2026-1201 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-1201 is a critical authentication bypass vulnerability in Hubitat Elevation C3, published on 22 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-1201 in the wild and no public exploit code.

Affected product: Hubitat Elevation C3. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-1201/ (Markdown: https://insights.sbomify.com/CVE-2026-1201/index.md)
```

## Sources

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

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