Skip to content
senn-techsenn-tech
Back to blog
Smart Home
Smart home and building automation2026-11-15· By Franz Senn

Philips Hue Bridge: Four Pwn2Own Flaws in the HomeKit Service, Check Your Firmware

The Zero Day Initiative (ZDI) published four advisories for the Philips Hue Bridge on 13 November 2026, all from the Pwn2Own contest. The bridge is the radio hub that Hue lights connect to in many homes, and it often doubles as the Zigbee gateway for Home Assistant.

Philips Hue logo
Philips Hue makes the Bridge whose HomeKit service the four ZDI advisories cover. (Quelle: Simple Icons (repo CC0), trademark: Philips Hue)

What ZDI describes

The affected component is the bridge's HomeKit service, which listens on TCP port 8080 by default. It handles pairing requests, and all four flaws sit there. ZDI lists them as follows (read on 15 Nov 2026 on the four advisory pages, where the CVE numbers and vectors also appear):

AdvisoryCVEFlawCVSS
ZDI-26-963CVE-2026-126978Heap buffer overflow in hap_pair_setup_handler, code execution8.8
ZDI-26-964CVE-2026-126979Integer underflow in chacha20_decrypt, code execution8.8
ZDI-26-965CVE-2026-126980Information disclosure through differing responses; per ZDI only usable together with other flaws for code execution6.5
ZDI-26-966CVE-2026-126981Authentication bypass because the order of pairing messages is not enforced8.1

All four carry the vector AV:A, with no login and no user interaction. According to the vector, the bridge is not reachable from the internet through these flaws, but it is from your own network. An infected device on your Wi-Fi, such as a guest phone or a vulnerable camera, could reach the hub that controls your lighting (our inference from the vector, not a case from the advisories).

Hue Bridge: the path into the four pairing flawsDevice on the samenetworkvector AV:A, not reachablefrom the internetHomeKit service, TCP8080accepts pairing requestswithout loginFour pairing flawsoverflow, underflow,information leak, authbypassOutcome per ZDIcode execution (8.8) orauthentication bypass (8.1)Countermeasurekeep firmware current, putthe Bridge on its ownnetwork
The flow follows the four ZDI advisories; the countermeasure is our own recommendation. (Quelle: ZDI-26-963 to ZDI-26-966)

What is known about the fix

ZDI names Bridge v2 software 1975170000 as the fixed build. Hue's release notes list that build under 16 Feb 2026 with the text "several small changes behind the scenes", so no mention of security fixes. ZDI says the flaws were reported on 28 Jul 2026, which is after that release, and the version numbers in the release notes have changed scheme since 27 Aug 2026 (latest 6.5.1978688000 from 12 Nov 2026, whose notes do not mention a security fix either). So we cannot show which build fixes what. What is certain: the bridge should be on the newest firmware.

What it means for Home Assistant

As far as we know, the Home Assistant Hue integration uses the bridge's local API (we did not re-read the Home Assistant documentation for this). That leaves the firmware untouched, so the integration does not protect against this. Two measures are cheap:

  • Check the firmware and turn on automatic updates in the Hue app.
  • Put the bridge in its own network or VLAN that only Home Assistant and the Hue app can reach. For VLANs, multicast and local integration, see Smart plugs for Home Assistant: Shelly, Tapo or Tasmota; separating networks can break mDNS discovery, so test it first.

Only people who use the bridge in Apple Home need the HomeKit service. Whether port 8080 can be switched off on the bridge is not something the advisories say, so that question is open.

Open points: We have not shown which firmware actually closes the flaws, whether the HomeKit service can be switched off, or whether Home Assistant uses the local API as described. We made no measurement on a bridge ourselves; this post summarizes the advisories.

Read next: Synology C2 Identity Edge Server and its CVSS discrepancy · Home Assistant Connect AUX-2 · the Bambu Lab H3C on a company network · Facebook and the Android gallery case in Italy

Further Reading

All five pages fetched on 15 November 2026.

Questions?
Can someone on the internet take over my Hue Bridge?+

Not directly, according to the advisories. All four flaws are rated adjacent-network (vector AV:A): the attacker has to be on the same network as the bridge, but needs no login there. A compromised device on your Wi-Fi is enough as a starting point.

How do I know whether my bridge has the fix?+

According to the Hue release notes, automatic updates are switched on in the app under Settings, Software update. ZDI names 1975170000 as the fixed build, and the latest Hue release notes list 6.5.1978688000 from 12 Nov 2026. If you are unsure, turn on automatic updates and check the version again after a few days.

Is it enough that the bridge is connected to Home Assistant?+

No. Home Assistant talks to the bridge over its local API, which does not touch the firmware. The flaw is in the bridge's own HomeKit service, so the firmware itself has to be current.