# CVE-2026-57473: Weak cryptography in Home Hub

> Attackers on the local network can brute-force weak credentials to intercept traffic and compromise connected camera credentials.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-xmw8-pxhc-cq64

## What is CVE-2026-57473?

CVE-2026-57473 is a medium-severity vulnerability in Reolink Home Hub, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability exists in the netclient and factory services of Reolink Home Hub (versions prior to v3.3.0.456_26031911) due to the possibility of brute-force cracking the credentials. This issue could allow attackers on the same local network to intercept traffic between the Hub and associated cameras and compromise the credentials of connected cameras.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2026-57473 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-57473 is a medium-severity vulnerability in Reolink Home Hub, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-57473 in the wild and no public exploit code.

Affected product: Reolink Home Hub. 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-57473/ (Markdown: https://insights.sbomify.com/CVE-2026-57473/index.md)
```

## Sources

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

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