CVE-2026-3558
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 · uneditedPhilips Hue Bridge HomeKit Accessory Protocol Transient Pairing Mode Authentication Bypass Vulnerability. This vulnerability allows network-adjacent attackers to bypass authentication on affected installations of Philips Hue Bridge. Authentication is not required to exploit this vulnerability. The specific flaw exists within the configuration of the HomeKit Accessory Protocol service, which listens on TCP port 8080 by default. The issue results from the lack of authentication prior to allowing access to functionality. An attacker can leverage this vulnerability to bypass authentication on the system. Was ZDI-CAN-28374.
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 · high confidenceThe Philips Hue Bridge contains an authentication bypass vulnerability in its HomeKit Accessory Protocol (HAP) service listening on TCP port 8080. The flaw allows network-adjacent attackers to bypass authentication by exploiting the lack of authentication checks in the transient pairing mode configuration, enabling unauthorized access to system functionality.
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< 1975170000CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device is Philips Hue Bridge V2Access the Hue Bridge web interface at http://<bridge-ip>/api/0/config or check the device label. The response contains a 'bridgeid' field - V2 bridges have an ID starting with 'ecb5fa' followed by 8 hex characters.Affected if The device is not a Philips Hue Bridge V2
-
Identify installed firmware versionSend a GET request to http://<bridge-ip>/api/0/config and locate the 'apiversion' or 'modelid' field. Alternatively, check the Hue app under Bridge settings > Software update to see the current firmware version number.Affected if Firmware version is present and less than 1975170000
-
Verify port 8080 is exposed on the networkRun nmap -p 8080 <bridge-ip> or nc -zv <bridge-ip> 8080 from a network-adjacent host to check if the HAP service port is accessible. This is the port where the vulnerability can be exploited.Affected if Port 8080 returns open and accepts connections from an untrusted network segment
-
Check network accessibility of the bridgeEnsure the Hue Bridge is not isolated on a dedicated VLAN or behind an ACL. Verify that untrusted devices on the same network can reach the bridge on port 8080.Affected if The bridge is reachable from network segments containing untrusted or unknown devices
A user is affected if they have a Philips Hue Bridge V2 running firmware below version 1975170000, with port 8080 exposed to untrusted network segments where an attacker could reach the device.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data1975170000
Restrict network access to the Hue Bridge on port 8080 using firewall rules or network segmentation to limit exposure to trusted devices only; apply vendor firmware updates when available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-3558 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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