QNAP patches critical QVR Pro flaw that could let remote attackers access vulnerable systems


QNAP has fixed a critical vulnerability in its QVR Pro surveillance software that could let remote attackers gain access to affected systems without authentication. The flaw, tracked as CVE-2026-22898, affects QVR Pro 2.7.x and is resolved in QVR Pro 2.7.4.1485 and later.

QNAP’s advisory describes the issue as a “missing authentication for critical function” bug. In plain terms, the software failed to enforce authentication on a sensitive function, which means an unauthenticated remote attacker could reach functionality that should have required prior login. QNAP credits FuzzingLabs for reporting the issue and lists the vulnerability as resolved.

The affected product scope appears narrow but important. QNAP’s advisory only lists QVR Pro 2.7.x as vulnerable, and the company does not mention older branches or other QNAP surveillance products in this notice. That makes this a focused but urgent patch for organizations using QVR Pro as part of their surveillance stack.

What the vulnerability means

A missing-authentication flaw in surveillance software can create more than a simple login bypass. Systems that manage cameras, recordings, user roles, and alerts often sit close to sensitive operational data and networked devices. If an attacker can access the system remotely, they may be able to tamper with surveillance settings, view or interfere with video operations, or use the compromised host as a foothold for further internal movement. QNAP’s advisory stops at saying remote attackers can gain access to the system, so anything beyond that remains a risk-based inference rather than a confirmed public exploitation path.

One useful correction to the sample draft: QNAP’s advisory does not say the flaw has been exploited in the wild, and it does not describe ransomware, botnet activity, or data-theft incidents tied to this CVE. The official notice only confirms the vulnerability, the affected versions, the fix, and the update steps.

Affected and fixed versions

ProductAffected versionsFixed version
QVR Pro2.7.x2.7.4.1485 and later

Source: QNAP security advisory QSA-26-07.

What admins should do now

QNAP’s recommendation is straightforward: update QVR Pro to the latest version. The company says administrators should sign in to QTS or QuTS hero, open App Center, search for QVR Pro, and click Update if the system still runs a vulnerable build. The Update button will not appear if the app is already current.

Practical priority steps:

  • Check whether any NAS devices run QVR Pro 2.7.x.
  • Upgrade affected systems to QVR Pro 2.7.4.1485 or later.
  • Review internet exposure for surveillance management interfaces and limit access where possible. This is a best-practice inference based on the remote nature of the flaw.
  • Confirm the updated build after patching and document which systems were remediated.
  • Explicitly advises updating to the latest version and provides the update workflow.

Why this deserves attention

QVR Pro is not just a background utility. It manages surveillance functions, which means compromise can affect visibility, evidence retention, and operational monitoring. Even when vendors publish a fix quickly, organizations often delay app-level updates on NAS platforms longer than core OS updates. That gap creates an opening attackers look for, especially when the flaw allows remote access without credentials. The severity rating in QNAP’s advisory is critical, which alone should move this patch near the top of the queue for affected users.

FAQ

What is CVE-2026-22898?

It is a critical missing-authentication vulnerability in QVR Pro that could let remote attackers gain access to the system.

Which versions are affected?

QNAP says QVR Pro 2.7.x is affected.

What version fixes the flaw?

QVR Pro 2.7.4.1485 and later fixes the issue.

Did QNAP say the flaw is under active attack?

The advisory does not say that. It only says the vulnerability was reported, affects QVR Pro 2.7.x, and is fixed in the newer version.

Readers help support VPNCentral. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help VPNCentral sustain the editorial team Read more

User forum

0 messages