Skip to main content
Menu
CVEs

CVE

Philips Hue Bridge Pro remote code execution via SQL injection in HTTP service

Affects Philips Hue Bridge Pro when its HTTP service, which listens on TCP port 443 by default, is in use. Fixed in firmware 6.1.2071524030 or later.

CVE-2026-118632

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

8.0HighCNA
Exploited
No known exploitation
Fix
Fixed in 6.1.2071524030
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The HTTP service is in use; it listens on TCP port 443 by default.

Published
Last modified
Reference
Last checked
0.86% · 58th percentile
13/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub

Summary

Philips Hue Bridge Pro has a SQL injection flaw in its HTTP service that lets an attacker on the same network segment run code as root. The attacker must log in first, but the login check can be bypassed.

Read the original description

Philips Hue Bridge Pro SQL Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Philips Hue Bridge Pro. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed.

The specific flaw exists within the HTTP service, which listens on TCP port 443 by default. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-33089.

Who should check

Teams running Philips Hue Bridge Pro firmware older than 6.1.2071524030, especially those with network-adjacent exposure. Check bridge firmware versions.

Read the source excerpt

“affected installations of Philips Hue Bridge Pro”

zerodayinitiative.com

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8/10CVSS 8.0
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The HTTP service is in use; it listens on TCP port 443 by default.
  • 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-118632 (Philips Hue Bridge Pro SQL Injection Remote Code Execution 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-118632 (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):
- The HTTP service is in use; it listens on TCP port 443 by default. (source: https://www.zerodayinitiative.com/advisories/ZDI-26-891/)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: adjacent access, low-privilege login, no user action.
CISA KEV: CVE-2026-118632 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-118632 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-891/
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-118632
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-118632"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Philips Hue Bridge Pro

    2071026000

Evidence 3

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-118632

Is CVE-2026-118632 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 SQL injection flaw in the bridge's HTTP service can allow code to be executed in the context of root on the affected bridge.Source: zerodayinitiative.com

Which versions are affected by CVE-2026-118632?

Hue Bridge Pro: version 2071026000.Source: cve.now feed data

Am I affected, and how do I check?

The flaw is in the HTTP service, which listens on TCP port 443 by default, so it matters only where that service is in use. The checked facts do not list affected version ranges, so compare the bridge's firmware version with the fixed version 6.1.2071524030.Source: zerodayinitiative.com

How do I fix CVE-2026-118632?

Update Bridge Pro firmware to version 6.1.2071524030 or later, which the vendor names as the fix.Source: zerodayinitiative.com