# CVE-2026-3555: Philips Hue Bridge Zigbee Stack Custom Command Handler Heap-based Buffer Overflow Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code on Philips Hue Bridge devices by exploiting a heap buffer overflow during Zigbee pairing.

- **Severity:** High 8.0 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-2q8v-6q3v-prjc

## What is CVE-2026-3555?

CVE-2026-3555 is a high-severity memory corruption vulnerability in Philips Hue Bridge, published on 13 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-3555?

It affects 1 product.


Products: Philips Hue Bridge V2 Firmware.

## How do I fix CVE-2026-3555?

No fix has been published for CVE-2026-3555 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-3555 being exploited?

There is no known exploitation of CVE-2026-3555 in the wild and no public exploit code.

## Other vulnerabilities in Philips Hue Bridge

- [CVE-2026-3556](https://insights.sbomify.com/CVE-2026-3556/): Philips Hue Bridge HomeKit Pair-Setup Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-3560](https://insights.sbomify.com/CVE-2026-3560/): Philips Hue Bridge HomeKit hk_hap_pair_storage_put Heap-based Buffer Overflow Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-3558](https://insights.sbomify.com/CVE-2026-3558/): Philips Hue Bridge HomeKit Accessory Protocol Transient Pairing Mode Authentication Bypass Vulnerability (high 8.1)
- [CVE-2026-3559](https://insights.sbomify.com/CVE-2026-3559/): Philips Hue Bridge HomeKit Accessory Protocol Static Nonce Authentication Bypass Vulnerability (high 8.1)
- [CVE-2026-3557](https://insights.sbomify.com/CVE-2026-3557/): Memory corruption in Hue Bridge (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3555 and fix it if it is affected.

What it is: CVE-2026-3555 is a high-severity memory corruption vulnerability in Philips Hue Bridge, published on 13 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-3555 in the wild and no public exploit code.

Affected product: Philips Hue Bridge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3555/ (Markdown: https://insights.sbomify.com/CVE-2026-3555/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3555
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3555
- OSV: https://osv.dev/vulnerability/CVE-2026-3555

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3555/
Summaries are generated and may contain mistakes; the official description above is the record.