# CVE-2026-5846: Hard-coded Cryptographic Key in Watchfire Controllers

> Hard-coded RSA keys in Watchfire controllers allow attackers to bypass authentication and decrypt HTTPS traffic to the web management interface.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 31 Jul 2026
- **Also known as:** GHSA-5qvx-vvgc-3mv8

## What is CVE-2026-5846?

CVE-2026-5846 is a high-severity vulnerability in Watchfire BC550, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The affected Watchfire Controller Software contains self-signed hard-coded RSA private keys and corresponding X.509 certificates used for authenticating and encrypting HTTPS/TLS connections to the controller's built-in web management interface. These keys are embedded in plaintext within the application patch binaries in the firmware directly from Watchfire's Remote Support filestore.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-5846?


## How do I fix CVE-2026-5846?

No fix has been published for CVE-2026-5846 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5846 being exploited?

There is no known exploitation of CVE-2026-5846 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5846 and fix it if it is affected.

What it is: CVE-2026-5846 is a high-severity vulnerability in Watchfire BC550, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-5846 in the wild and no public exploit code.

Affected product: Watchfire BC550. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5846/ (Markdown: https://insights.sbomify.com/CVE-2026-5846/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5846
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5846
- OSV: https://osv.dev/vulnerability/CVE-2026-5846

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5846/
Summaries are generated and may contain mistakes; the official description above is the record.