Skip to main content

Hybrid Backup Sync CVE-2025-62841

| EUVDEUVD-2025-211209 HIGH
Use of Hard-coded Cryptographic Key (CWE-321)
2026-10-29 qnap GHSA-rv3x-2h7v-368w
8.7
CVSS 4.0 · Vendor: qnap
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain adjacent-network access to NAS
  2. Exploit
    Recover hard-coded cryptographic key from software
  3. Execution
    Decrypt or forge protected data/channel
  4. Impact
    Compromise confidentiality and integrity of system

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Key management, no hard-coded keys
Exploitation Conditions

Exploitation requires network adjacency to the QNAP NAS running HBS 3 / Hybrid Backup Sync (AV:A) - the attacker must be on the same local or logical network segment, not arbitrary internet distance, unless the affected service is explicitly exposed through port-forwarding or remote-access configuration. The core prerequisite is possession of the hard-coded cryptographic key (CWE-321), which is embedded in the shipped software and therefore identical for, and recoverable from, every installation. No authentication and no user interaction are needed (PR:N/UI:N), and complexity is low (AC:L). The primary limiting factors are the adjacency requirement and the need to run an affected version below the fixed builds (Hybrid Backup Sync <26.4.1.563 / <26.4.0.521, HBS 3 <26.4.0.521); the exact feature or protocol in which the key is used is not described in the available sources.

Impact

This is a serious-but-conditional flaw rather than an internet-wide emergency. The input provides a CVSS 4.0 vector (8.7) with AV:A, AC:L, AT:N, PR:N, UI:N and VC:H/VI:H/VA:H - unauthenticated, low-complexity access with full confidentiality, integrity and availability impact on the vulnerable system, but the Adjacent (AV:A) attack vector means the attacker must reach the device over a local/logical network segment rather than directly across the internet. CWE-321 (use of hard-coded cryptographic key) is inherently high-value because the key is identical across all deployments and recoverable from the shared software, so once published it affects every installed instance uniformly. However, the real-world escalators are absent or unstated: there is no EPSS score in the input, the CVE is NOT in CISA KEV, and no PoC or exploit reference is listed, so this must be treated as 'no public exploit identified at time of analysis' - not active exploitation. The vendor-assigned priority is 'this_week' (not act_now/emergency) and a patch is available, which is consistent with a high-severity issue that warrants prompt but not drop-everything remediation. One point to verify with the vendor: the description says 'remote attackers' while the CVSS vector specifies Adjacent (AV:A) access, so confirm whether exposed/port-forwarded QNAP services widen the practical reach beyond the LAN.

Exploit ScenarioDerived

An attacker positioned on the same local network as a QNAP NAS (for example via a compromised LAN host or a device exposed on an untrusted segment) leverages the cryptographic key embedded in HBS 3 / Hybrid Backup Sync - a key shared across all installations - to break the confidentiality or integrity of protected communications or data on the appliance. Because authentication and user interaction are not required (PR:N/UI:N), a single adjacent, low-complexity action can fully compromise the targeted system. No public exploit code is identified in the available sources, and the precise trigger is not described.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 29, 2026

Hard-coded cryptographic key use in QNAP HBS 3 Hybrid Backup Sync lets a network-adjacent, unauthenticated attacker compromise the confidentiality, integrity and availability of the NAS. Installations running HBS 3 Hybrid Backup Sync below 26.4.0.521, or Hybrid Backup Sync below 26.4.0.521 / 26.4.1.563, are affected; because the key ships inside the software it is identical on every install and recoverable from the package, so no credentials or user interaction are needed. There is no public exploit identified at time of analysis, but the vendor has released fixed builds and the exposure is rated 8.7 (CVSS 4.0) with high impact across all three pillars.

RemediationAI

Update the application to a fixed build: HBS 3 Hybrid Backup Sync 26.4.0.521 or later, and Hybrid Backup Sync 26.4.0.521 or later or 26.4.1.563 or later depending on the branch installed - QNAP lists the fix as available and distributes it through the App Center release channels described in the release notes at https://www.qnap.com/en/app-release-notes?keyword=HBS%203&app=HybridBackup&product-line=nas and https://www.qnap.com/en/app-release-notes?keyword=Hybrid&app=HybridBackup&product-line=nas. Because the key is baked into the shipped software and is common to every deployment, the update is the only complete fix - there is no per-device key rotation that an administrator can perform to neutralise an already-extracted key on an unpatched build. Until the upgrade is applied, reduce the adjacency prerequisite: keep NAS management and HBS traffic on a segmented VLAN or restricted management network reachable only from trusted hosts, and remove any port-forwarding or remote-access exposure of the HBS service from the internet; the trade-off is that off-site backup jobs and remote administration then require a VPN or jump host. Restricting source addresses at the NAS firewall to known backup peers limits who can reach the service but does not help if a permitted peer is itself compromised, and none of these measures remove the underlying hard-coded key.

Affected VersionsENISA

Hybrid Backup Sync 26.4.x <26.4.1.563
HBS 3 Hybrid Backup Sync 26.4.x <26.4.0.521
Hybrid Backup Sync 26.4.x <26.4.0.521

Affected Packages

euvd hbs_3_hybrid_backup_sync fix: 26.4.0.521
euvd hybrid_backup_sync fix: 26.4.0.521, 26.4.1.563

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is classified CWE-321, use of a hard-coded cryptographic key: rather than generating or provisioning per-device key material, HBS 3 Hybrid Backup Sync embeds a static key in the shipped application. Any party who obtains the application package can extract that key, and because it is shared across all installations it becomes a universal secret rather than a per-device one - compromise of one install's key material effectively applies to every other install at the same build. The CVSS 4.0 vector (AV:A/AC:L/AT:N/PR:N/UI:N, with high confidentiality, integrity and availability impact, and no subsequent-system impact) describes a low-complexity attack launched from an adjacent network segment with no privileges and no user interaction, so severity reflects the value of what the key protects rather than any complicated trigger. The sources do not state which internal feature, protocol or stored-data path actually consumes the hard-coded key, so the precise mechanism by which an attacker converts knowledge of the key into system compromise is not described in the available evidence; likewise, the assessment notes adjacency is the practical gate unless the HBS service has been deliberately port-forwarded or exposed through remote-access configuration.

Know when Hbs 3 Hybrid Backup Sync gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (qnap) PRIMARY 8.7 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 8.8 HIGH

Adjacent, low-complexity, unauthenticated access to a shared hard-coded key yields full C/I/A impact on the appliance; scope unchanged as impact stays within the vulnerable system.

3.1 AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (qnap).

CVSS VectorVendor: qnap

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 29, 2026 - 08:16 EUVD
CVE Published
Oct 29, 2026 - 07:40 cve.org
HIGH 8.7

DescriptionCVE.org

An use of hard-coded cryptographic key vulnerability has been reported to affect HBS 3 Hybrid Backup Sync and Hybrid Backup Sync. If exploited, the vulnerability could allow remote attackers to compromise the security of the system.

We have already fixed the vulnerability in the following version: HBS 3 Hybrid Backup Sync 26.4.0.521 and later Hybrid Backup Sync 26.4.0.521 and later Hybrid Backup Sync 26.4.1.563 and later

Executive ViewAI

Why It Matters

QNAP HBS 3 Hybrid Backup Sync contains a hard-coded cryptographic key that could allow network-adjacent attackers to compromise backups and NAS data. This affects all installations below version 26.4.0.521, meaning backup confidentiality, integrity, and availability are at risk across the organization. Leadership should prioritize patching to prevent potential data breaches or backup corruption.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 84% exploitable
Prevalence
Medium
QNAP NAS backup app; common on QNAP appliances but not everywhere
Social Media
2
Sightings
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy