dbcve.org
Hue Bridge V2 FirmwareOperating system · Philips

CVE-2026-3555

HIGH · 8.0 CVSS v3.0 Published 2026-03-16
Fix available
A fix is available. Upgrade to 1975170000 or later.
See remediation →
83/100
Remediation priority · High
No privileges

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
Philips Hue Bridge Zigbee Stack Custom Command Handler Heap-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of Philips Hue Bridge. User interaction is required to exploit this vulnerability in that the user must initiate the device pairing process. The specific flaw exists within the handling of custom Zigbee ZCL frames in the Model Info download functionality. The issue results from the lack of proper validation of the size of data prior to copying it to a fixed-size heap buffer. An attacker can leverage this vulnerability to execute code in the context of the device. Was ZDI-CAN-28276.

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 · moderate confidence

A heap-based buffer overflow vulnerability exists in the Philips Hue Bridge Zigbee stack's custom command handler. The flaw is in the handling of custom Zigbee ZCL frames during Model Info download functionality, where the size of data is not validated before being copied into a fixed-size heap buffer. Network-adjacent attackers can exploit this to execute arbitrary code in the context of the device, but require the user to initiate the device pairing process.

MitigationApply vendor-supplied firmware patches when available; until then, restrict network access to the Hue Bridge and avoid pairing with untrusted devices.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Hue Bridge V2 FirmwareOperating system
Affected:< 1975170000

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
Adjacent
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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. Confirm device model is Philips Hue Bridge V2
    Inspect the physical device label or check the device details via the Philips Hue app or web interface at http://<bridge-ip>/api/<username>/config to identify the device model name and serial number.
    Affected if The device is not a Philips Hue Bridge V2 model.
  2. Retrieve the installed firmware version
    Send a GET request to the Hue Bridge API endpoint: http://<bridge-ip>/api/<username>/config and locate the 'apiversion' or 'swversion' field in the JSON response, or check via the Philips Hue mobile app under Settings > Bridge settings.
    Affected if The firmware version string is present and less than 1975170000.
  3. Compare firmware version against affected range
    Parse the numeric firmware version from the previous step. Philips Hue Bridge V2 firmware versions are numeric (e.g., 1975160000). Compare this number to 1975170000.
    Affected if The installed firmware version is below 1975170000.
  4. Verify Model Info download functionality is accessible
    Check if the Bridge API responds to endpoints related to model info or OTA queries - typically /api/<username>/ota or /api/<username>/modelinfo - or observe network traffic during normal device operation.
    Affected if The Model Info download feature is present and accessible on the device.

The device is affected if it is a Philips Hue Bridge V2 running firmware version below 1975170000 and the Model Info download feature is accessible on the network.

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
Upgrade available Upgrade to 1975170000 or later
Fixed in 1975170000
Interim mitigation

Apply vendor-supplied firmware patches when available; until then, restrict network access to the Hue Bridge and avoid pairing with untrusted devices.

Recommended fix Moderate confidence

Hue Bridge V2 Firmware 1975170000 or later

  1. 1. Identify the current firmware version of the Philips Hue Bridge V2 by accessing the Hue Bridge web interface or using the Hue app.
  2. 2. Navigate to Settings > Hue Bridge > Software update (or equivalent path in the current Hue app interface).
  3. 3. Check if a new firmware update is available. The fixed firmware version is 1975170000 or later.
  4. 4. If an update is available, initiate the firmware update through the official Hue app or bridge settings.
  5. 5. Allow the update to complete fully - do not power off the bridge during the update process.
  6. 6. After the update completes, verify the firmware version has been updated to 1975170000 or higher.
  7. 7. As a secondary mitigation, ensure the Hue Bridge is not directly exposed to untrusted networks and limit pairing requests from unknown devices until the update is applied.
Caveat Standard firmware update; no major breaking changes expected for normal Hue functionality

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

Fix this in Hue Bridge V2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3555 — 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-3555 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