Skip to main content
CVE-2026-1201VulnerabilityPublished Updated

CVE-2026-1201: Hubitat Elevation C3 · Insecure Direct Object Reference

Affects Hubitat Elevation C3Source CVE Database V5

0

Not known to be exploited · CVSS 9.4 Critical : upgrade to 2.4.2.157 as a priority.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.2.157
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade Elevation to 2.4.2.157.

Affected software

ProductAffectedFixed in
HubitatElevation C3Affected
  • <2.4.2.157
Fixed in
  • 2.4.2.157
HubitatElevation C4Affected
  • <2.4.2.157
Fixed in
  • 2.4.2.157
HubitatElevation C5Affected
  • <2.4.2.157
Fixed in
  • 2.4.2.157
HubitatElevation C7Affected
  • <2.4.2.157
Fixed in
  • 2.4.2.157
HubitatElevation C8Affected
  • <2.4.2.157
Fixed in
  • 2.4.2.157
HubitatElevation C8 proAffected
  • <2.4.2.157
Fixed in
  • 2.4.2.157

AI-suggested

1. Immediately update all Hubitat Elevation C3 controllers to version 2.4.2.157 or later once available, as this version addresses the vulnerability. 2. Enforce strict authentication and authorization policies, ensuring that user privileges are minimized and regularly reviewed to reduce the risk of credential misuse. 3. Implement network segmentation to isolate smart home controllers from critical IT infrastructure, limiting the impact of a compromised device. 4. Monitor network traffic and device logs for anomalous commands or access patterns indicative of authorization bypass attempts. 5. Employ multi-factor authentication (MFA) for accessing the controller management interfaces to reduce the risk of credential compromise. 6. Conduct regular security audits and penetration testing focused on IoT and smart home devices to identify similar weaknesses. 7. Educate users and administrators about phishing and credential security to prevent attackers from gaining authenticated access. 8. If patching is delayed, consider disabling remote access features or restricting access to trusted IP addresses to reduce exposure. 9. Collaborate with Hubitat support and subscribe to security advisories for timely updates on patches and mitigations.

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.

References

Community reviews

Loading reviews…