dbcve.org
Qvr ProApplication · Qnap

CVE-2026-22898

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 2.7.4.1485 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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 missing authentication for critical function vulnerability has been reported to affect QVR Pro. The remote attackers can then exploit the vulnerability to gain access to the system. We have already fixed the vulnerability in the following version: QVR Pro 2.7.4.14 and later

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 · moderate confidence

This is a missing authentication vulnerability in QVR Pro (QNAP's video surveillance solution) where a critical function lacks proper authentication checks. Remote attackers can exploit this by sending crafted requests to the unauthenticated endpoint, potentially gaining administrative access to the system without any credentials.

MitigationUpgrade QVR Pro to version 2.7.4.14 or later to apply the vendor patch. If immediate patching is not possible, restrict network access to QVR Pro management interfaces using firewall rules or VPN access to limit exposure to untrusted networks.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qvr ProApplication
Affected:>= 2.7.1.1259, < 2.7.4.1485

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Confirm QVR Pro is installed
    Access the QNAP admin interface and navigate to the applications section, or use the QNAP command line to list installed QPKG packages to verify QVR Pro is present on the system.
    Affected if QVR Pro is not installed on the QNAP device.
  2. Identify installed QVR Pro version
    In the QNAP admin interface, go to QVR Pro application settings and locate the version information displayed in the About or System Status section.
    Affected if The displayed version falls within the range >= 2.7.1.1259 and < 2.7.4.1485.
  3. Verify version is in affected range
    Compare your identified version number against the affected range: versions 2.7.1.1259 through 2.7.4.1484 are vulnerable. Versions below 2.7.1.1259 or at/above 2.7.4.1485 are not affected.
    Affected if The installed version is 2.7.1.1259 or higher but lower than 2.7.4.1485.
  4. Assess network exposure of QVR Pro management interface
    Check firewall rules, port forwarding configurations, or network access controls to determine if the QVR Pro web interface (typically ports 8081, 8082, or 443) is accessible from untrusted networks or the internet.
    Affected if The QVR Pro management interface is exposed to untrusted networks without proper access restrictions.

You are affected if QVR Pro is installed and the installed version is between 2.7.1.1259 and 2.7.4.1484 inclusive, and the management interface is network-accessible.

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
Upgrade available Upgrade to 2.7.4.1485 or later
Fixed in 2.7.4.1485
Interim mitigation

Upgrade QVR Pro to version 2.7.4.14 or later to apply the vendor patch. If immediate patching is not possible, restrict network access to QVR Pro management interfaces using firewall rules or VPN access to limit exposure to untrusted networks.

Recommended fix High confidence

QVR Pro 2.7.4.14 or later

  1. 1. Log in to the QNAP QVR Pro management interface
  2. 2. Navigate to System Settings > System Update or the appropriate update section
  3. 3. Check the current installed version of QVR Pro to confirm it is within the affected range (>= 2.7.1.1259 and < 2.7.4.1485)
  4. 4. Initiate a system update to check for available updates
  5. 5. Upgrade QVR Pro to version 2.7.4.14 or later
  6. 6. After the update completes, verify the new version is installed and the vulnerability is resolved

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

Fix this in Qvr Pro Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22898 — 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-22898 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