# CVE-2026-118631: Philips Hue Bridge Pro Argument Injection Restricted File Write Vulnerability

Status: published. Published: 2026-11-12. Updated: 2026-11-12.

Philips Hue Bridge Pro Argument Injection Restricted File Write Vulnerability. This vulnerability allows local attackers to modify files on affected installations of Philips Hue Bridge Pro. An attacker must first obtain the ability to execute low-privileged code within a container on the target system, in order to exploit this vulnerability.

The specific flaw exists within the factory data service, which listens on TCP port 5001 by default. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to modify files in the context of the service account. Was ZDI-CAN-33090.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Philips / Hue Bridge Pro: 2071026000 (affected). Source: CNA: zdi

## Severity and prioritization

- CVSS 3.0: 3.8 (low); CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N; source: CNA: zdi

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-88

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.zerodayinitiative.com/advisories/ZDI-26-890/ (CNA: zdi; x_research-advisory)

## Provenance

- CNA: zdi: https://www.cve.org/CVERecord?id=CVE-2026-118631; retrieved 2026-11-12; source updated 2026-11-12

Revision: 0c1cef19c22f9604bb0b1d90c02e6603788e33e0519f3c612cb2aafb39349164

Canonical: https://y2.dev/cve/CVE-2026-118631

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.