dbcve.org
CWE-1391Weakness · CWE-1391

CVE-2026-57473

MEDIUM · 5.8 CVSS v4.0 Published 2026-06-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The netclient and factory services in Reolink Home Hub versions prior to v3.3.0.456_26031911 contain a vulnerability allowing brute-force credential cracking. Attackers on the same local network can intercept unencrypted or poorly protected traffic between the Hub and associated cameras, enabling compromise of camera credentials.

MitigationUpgrade Reolink Home Hub firmware to v3.3.0.456_26031911 or later. After updating, rotate credentials for all connected cameras to ensure compromised credentials are no longer valid.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Reolink Home Hub device on your network
    Log into your router or use a network scanner to locate a device with hostname or model identifier matching 'Reolink Home Hub' or 'RHH', or physically inspect your device for the Reolink Home Hub label
    Affected if No Reolink Home Hub device is found on the network - you are not affected
  2. Check installed firmware version
    Access the Reolink Home Hub web interface or mobile app, navigate to Settings > Device Info > Firmware Version, and record the displayed version number
    Affected if The firmware version is prior to v3.3.0.456_26031911 (for example, v3.2.x.x or any version below v3.3.0.456_26031911) - you are likely affected
  3. Verify device is accessible on local network
    Confirm the Reolink Home Hub has an IP address on your local network and is responding to ping or web requests from other devices on the same subnet
    Affected if The device is actively connected to a local network with other devices - the vulnerability requires local network access to intercept traffic
  4. Confirm camera connections exist
    In the Reolink Home Hub interface, check the camera list or paired devices section to see if any IP cameras are registered and communicating with the Hub
    Affected if One or more cameras are paired with the Hub - the flaw allows attackers to crack credentials used for these camera connections

You are affected if you have a Reolink Home Hub running firmware version earlier than v3.3.0.456_26031911 and have cameras connected on the same local network, as attackers on that network could intercept and crack camera credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Reolink Home Hub firmware to v3.3.0.456_26031911 or later. After updating, rotate credentials for all connected cameras to ensure compromised credentials are no longer valid.

Recommended fix High confidence

v3.3.0.456_26031911

  1. Access the Reolink Home Hub management interface through a web browser
  2. Navigate to the firmware settings or system update section
  3. Check the current firmware version to confirm it is prior to v3.3.0.456_26031911
  4. Download the firmware update v3.3.0.456_26031911 or later from the official Reolink support website
  5. Upload and apply the firmware update following the on-screen instructions
  6. Wait for the device to reboot and complete the update process
  7. Verify the firmware version has been updated to v3.3.0.456_26031911 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57473 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57473 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data