VulnerabilityPublished 13 Mar 2026Updated 16 Mar 2026

CVE-2026-3559: Philips Hue Bridge · Reusing a Nonce, Key Pair in Encryption

Affects Philips Hue BridgeSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Adjacent
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PhilipsHue Bridge	Affected =1.73.1973146020	Fixed in–

AI-suggested

Users should monitor Philips' official advisories for updates regarding remediation. Until a fix is available, limiting network exposure of the Philips Hue Bridge, such as restricting access to trusted networks and blocking TCP port 8080 from untrusted sources, can reduce risk.

Description

CVE-2026-3559 is a high-severity vulnerability in the Philips Hue Bridge version 1.73.1973146020 that allows network-adjacent attackers to bypass authentication without any privileges. The flaw is due to the reuse of a static nonce in the SRP authentication mechanism of the HomeKit Accessory Protocol service, which listens on TCP port 8080 by default. This static nonce enables attackers to circumvent authentication controls, potentially gaining unauthorized access to the device. There is no indication that a patch or official fix is currently available. Exploits in the wild have not been reported as of the publication date.

Impact

Successful exploitation allows an attacker within the network to bypass authentication on the Philips Hue Bridge device, potentially leading to unauthorized control or access to the device's functions and data. The vulnerability compromises confidentiality and integrity but does not impact availability. Since authentication is bypassed, attackers could manipulate device settings or intercept sensitive information handled by the bridge.

Summary

This vulnerability arises from improper use of a static nonce in the Secure Remote Password (SRP) authentication mechanism within the HomeKit Accessory Protocol on Philips Hue Bridge devices. The affected service listens on TCP port 8080 and does not require authentication to be exploited. By reusing the nonce, an attacker can bypass authentication, violating the intended security model. The issue is tracked as CWE-323 (Reusing a Nonce, Key Pair in Encryption). The CVSS v3.0 base score is 8.1, indicating a high impact with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Confidentiality and integrity impacts are high, while availability is not affected.

CWE-323Reusing a Nonce, Key Pair in Encryption (opens in a new tab)
Base weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
Nonces should be used for the present occasion and only once.
Implementation
Refuse to reuse nonce values.
Implementation
Use techniques such as requiring incrementing, time based and/or challenge response to assure uniqueness of nonces.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

zerodayinitiative.com/advisories/ZDI-26-157/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 May 2026, 20:24 UTC

WeaknessesCWE-323

Technical details

References

Community reviews

Related threats