CVE
Philips Hue Bridge Pro authentication bypass in HTTP service
Affects Philips Hue Bridge Pro devices whose HTTP service on TCP port 443 is enabled, which is the default. Fixed in Bridge Pro firmware 6.1.2071524030 or later.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 6.1.2071524030
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.1.2071524030.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.38% · 31st percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Philips Hue Bridge Pro has a flaw in its HTTP service, which listens on TCP port 443 by default, that lets an attacker bypass authentication. An attacker on the same network segment can exploit it without logging in or any user action, gaining the same access as an authenticated user; the bypass is not known to be used in attacks.
Read the original description
Philips Hue Bridge Pro Protection Mechanism Failure Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Philips Hue Bridge Pro. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the HTTP service, which listens on TCP port 443 by default. The issue results from the failure to apply a protection mechanism. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-33086.
Who should check
Anyone running Philips Hue Bridge Pro firmware with the HTTP service on TCP port 443 reachable from an adjacent network.
Read the source excerpt
“This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Philips Hue Bridge Pro.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.1.2071524030.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-122044 (Philips Hue Bridge Pro Protection Mechanism Failure Authentication Bypass Vulnerability), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-122044 (entry last updated 2026-11-12):
Affected:
- Philips Hue Bridge Pro: versions 2071026000
Fixed versions: 6.1.2071524030.
Conditions (all must be true for the bug to be hit):
- Philips Hue Bridge Pro with the HTTP service on TCP port 443 (listens on 443 by default) (source: https://www.zerodayinitiative.com/advisories/ZDI-26-892/)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-122044 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-122044 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.zerodayinitiative.com/advisories/ZDI-26-892/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-122044
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-122044"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Philips Hue Bridge Pro
2071026000
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-122044
Is CVE-2026-122044 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in the Hue Bridge Pro's HTTP service on TCP port 443 lets an attacker get past the login protections on the device. The advisory describes this as an authentication bypass.Source: zerodayinitiative.com
Which versions are affected by CVE-2026-122044?
Hue Bridge Pro: version 2071026000.Source: cve.now feed data
Am I affected, and how do I check?
Affected devices are Philips Hue Bridge Pro units running firmware older than 6.1.2071524030 with the HTTP service listening on TCP port 443, which is the default. To check, look up the firmware version in the Hue app or the bridge settings and compare it to 6.1.2071524030.Source: zerodayinitiative.com
How do I fix CVE-2026-122044?
Update the Hue Bridge Pro to firmware version 6.1.2071524030 or later, which is the version named in the vendor's fix.Source: zerodayinitiative.com