Skip to content
IoT

CVE-2026-1201

9.4
Critical
EPSS 0.45%Patch availableJan 23, 2026

Auth bypass via user-controlled key in Hubitat Elevation enables unauthorized device control.

common questions

Is CVE-2026-1201 being exploited?

Not confirmed. CVE-2026-1201 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.45% probability of exploitation in the next 30 days.

How severe is CVE-2026-1201?

CVE-2026-1201 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-1201?

Yes. A fix has been recorded for CVE-2026-1201. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-1201 affect?

CVE-2026-1201 affects Hubitat Elevation (pre-2.4.2.157). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1201?

Upgrade to v2.4.2.157 or newer.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Hubitat Elevation (pre-2.4.2.157)
impact

Remote authenticated user can bypass controls by manipulating client requests to affect devices outside their scope.

action required

Immediate action required

affected versions
Hubitat Elevation C3
  • affected< 2.4.2.157
Hubitat Elevation C4
  • affected< 2.4.2.157
Hubitat Elevation C5
  • affected< 2.4.2.157
Hubitat Elevation C7
  • affected< 2.4.2.157
Hubitat Elevation C8
  • affected< 2.4.2.157
Hubitat Elevation C8 pro
  • affected< 2.4.2.157

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free