CVE-2026-5846: Watchfire BC550 · Use of Hard-coded Cryptographic Key
Affects Watchfire BC550Source CVE Database V5
Not known to be exploited · CVSS 5.7 Medium.
Data as of 29 Oct 2026, 10:10 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 30 Jul 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 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WatchfireBC550 | Affected
| Fixed in– |
| WatchfireBC750 | Affected
| Fixed in– |
| WatchfireBC760 | Affected
| Fixed in– |
| WatchfireBC760DC | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict access to the device's management interface to trusted networks and users, and monitor for unauthorized access attempts.
Description
The Watchfire BC550 controller software version 12.30 contains hard-coded self-signed RSA private keys and X.509 certificates embedded in plaintext within its firmware. These cryptographic materials are used for HTTPS/TLS authentication and encryption of the device's web management interface. The presence of hard-coded keys poses a risk of unauthorized access if the keys are extracted and reused by attackers.