CVE-2025-54148VulnerabilityPublished 11 Feb 2026

CVE-2025-54148: QNAP Systems Qsync Central · CWE-476

Affects QNAP Systems Qsync CentralSource CVE Database V5

Not known to be exploited · CVSS 1.3 Low : upgrade to 5.0.0.4 ( 2026/01/20 ) when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

1.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 5.0.0.4 ( 2026/01/20 )

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: Unreported

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: Unreported: Based on threat intelligence sources each of the following must apply: · No knowledge of publicly available proof-of-concept · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade QNAP Systems Qsync Central to 5.0.0.4 ( 2026/01/20 ).

Affected software

Product	Affected	Fixed in
QNAP Systems Inc.Qsync Central	Affected =5.0.x.x	Fixed in 5.0.0.4 ( 2026/01/20 )

AI-suggested

To mitigate this vulnerability, European organizations should: 1) Immediately upgrade Qsync Central to version 5.0.0.4 or later where the vulnerability is patched. 2) Enforce strict access controls and multi-factor authentication (MFA) for all user accounts to reduce the risk of unauthorized access. 3) Regularly audit user accounts and permissions to detect and remove any unauthorized or dormant accounts. 4) Monitor Qsync Central logs for unusual activity that could indicate attempted exploitation or account compromise. 5) Implement network segmentation to limit exposure of Qsync Central services to trusted internal networks or VPNs. 6) Employ intrusion detection/prevention systems (IDS/IPS) to detect anomalous traffic patterns targeting Qsync Central. 7) Educate users on secure credential practices to prevent account compromise. These steps go beyond generic advice by focusing on access control hardening and monitoring tailored to the vulnerability's exploitation requirements.

Description

CVE-2025-54148 is a NULL pointer dereference vulnerability in QNAP Systems Inc. 's Qsync Central product, specifically affecting version 5.0.x.x. A remote attacker with a valid user account can exploit this flaw to cause a denial-of-service (DoS) condition, crashing or disrupting the service. The vulnerability does not require user interaction and has a low CVSS score of 1.3, indicating limited impact and ease of exploitation. The issue has been fixed in Qsync Central version 5.0.

Impact

For European organizations, the primary impact of this vulnerability is the potential denial-of-service of Qsync Central services, which could disrupt file synchronization and backup operations. Organizations relying heavily on QNAP NAS devices and Qsync Central for data availability and collaboration may experience operational downtime, affecting productivity. However, since exploitation requires authenticated access, the risk is mitigated if strong access controls and account management practices are in place. The low severity score indicates limited risk to confidentiality and integrity. Nonetheless, disruption of availability can have cascading effects, especially in sectors like finance, healthcare, and critical infrastructure where data synchronization is vital. Organizations with large deployments of QNAP devices or those in regulated industries should prioritize patching to avoid service interruptions and potential compliance issues related to data availability.

CWE-476NULL Pointer Dereference (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #13OWASP Top 10 A10:2025: Mishandling of Exceptional Conditions (opens in a new tab)
The product dereferences a pointer that it expects to be valid but is NULL.
Implementation
For any pointers that could have been modified or provided from a function that can return NULL, check the pointer for NULL before use. When working with a multithreaded or otherwise asynchronous environment, ensure that proper locking APIs are used to lock before the check, and unlock when it has finished.
Requirements
Select a programming language that is not susceptible to these issues.
Implementation
Check the results of all functions that return a value and verify that the value is non-null before acting upon it.
OWASP Cheat Sheets
Logging (opens in a new tab)
Error Handling (opens in a new tab)
OWASP ASVS 4.0.3
V11.1.7 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

qnap.com/en/security-advisory/qsa-26-02 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Feb 2026, 15:06 UTC

WeaknessesCWE-476

Technical details

References

Community reviews

Related threats