dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-1201

CRITICAL · 9.4 CVSS v4.0 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Hubitat Elevation home automation controllers prior to version 2.4.2.157 contain an authorization bypass vulnerability where an authenticated remote user can manipulate client-side requests using a user-controlled key to access and control connected devices outside their authorized permission scope. This allows privilege escalation within the device control framework.

MitigationUpdate Hubitat Elevation controllers to version 2.4.2.157 or later to patch the authorization bypass. Review user access controls and device permissions to ensure no unauthorized access occurred prior to patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Hubitat Elevation firmware version
    Log into the Hubitat web interface and navigate to Settings > Hub Details, or use the hub status page to view the current firmware version number.
    Affected if The installed version is lower than 2.4.2.157
  2. Verify if remote access is enabled
    Check the Hubitat configuration for cloud or remote access settings (typically under Settings > Remote Access) to determine if the hub is accessible from outside the local network.
    Affected if Remote access is enabled and the firmware is below 2.4.2.157
  3. Review user accounts and permissions
    Navigate to Settings > Users in the Hubitat interface and examine all user accounts to verify each user has only the permissions intended for their role.
    Affected if Multiple user accounts exist with differing permission levels and the firmware is below 2.4.2.157
  4. Audit device sharing or external integrations
    Review device sharing settings or any third-party integrations (such as Hubitat Package Manager integrations or external smart home platform links) to confirm devices are not shared beyond intended users.
    Affected if Devices are shared with other users or external platforms and the firmware is below 2.4.2.157

A Hubitat Elevation controller is affected if it is running firmware prior to 2.4.2.157 and has remote access enabled or multiple user accounts configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Hubitat Elevation controllers to version 2.4.2.157 or later to patch the authorization bypass. Review user access controls and device permissions to ensure no unauthorized access occurred prior to patching.

Recommended fix High confidence

Hubitat Elevation firmware version 2.4.2.157

  1. Identify the current Hubitat Elevation firmware version by navigating to the device's web interface and checking the firmware information
  2. Download firmware version 2.4.2.157 or later from the official Hubitat website or through the built-in firmware update mechanism
  3. Back up the current hub configuration through the web interface before performing the update
  4. Initiate the firmware update through the Hubitat Elevation web interface or using the official update process
  5. Verify the update was successful by confirming the new firmware version displays as 2.4.2.157 or later
  6. Test that device access controls are functioning correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1201 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1201 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data