Skip to main content
Mallory
CriticalVulnerability

CVE-2026-22898: Missing Authentication in QNAP QVR Pro

Published Mar 20, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS0.72%54th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
QNAP Systems
IdentifiersCVE-2026-22898CWE-306 · Missing Authentication for…

CVE-2026-22898 is a missing authentication for critical function vulnerability affecting QNAP QVR Pro 2.7.x. The flaw has been described as an exposed dangerous method within the QVRPro Plugin that can be reached without authentication. On affected installations, a remote or network-adjacent attacker can invoke the vulnerable functionality without valid credentials and gain unauthorized access to the system. Available reporting also indicates the issue can lead to arbitrary code execution in the context of the postgres user on affected QNAP TS-453E installations running the vulnerable QVR Pro component.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to bypass intended access controls and obtain unauthorized access to the affected system. Reported consequences include arbitrary code execution in the context of the postgres user, compromise of confidentiality, integrity, and availability, access to surveillance functionality and data, manipulation of surveillance configuration, and potential follow-on activity against other reachable systems.

Mitigation

If you can’t patch tonight, do this now.

Apply the latest available QVR Pro update immediately. Until patching is completed, reduce exposure of the QVR Pro service to untrusted networks, restrict access to trusted management paths only, and closely monitor affected NAS and surveillance environments for unauthorized access or abnormal activity. Operationally, administrators can use QTS or QuTS hero App Center to locate and install the corrected QVR Pro release.

Remediation

Patch, then assume compromise.

Upgrade QVR Pro 2.7.x to QVR Pro 2.7.4.1485 or later. Vendor information also states the issue is fixed in QVR Pro 2.7.4.14 and later; the more specific fixed release cited in the advisory context is 2.7.4.1485. Administrators should apply the vendor-provided update through the QTS or QuTS hero App Center and verify that the update completed successfully.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
QNAP SystemsQvr Proapplication
FAQ

Frequently asked questions

Is CVE-2026-22898 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-22898 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-22898?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-22898.
Is there a patch for CVE-2026-22898?
Upgrade QVR Pro 2.7.x to QVR Pro 2.7.4.1485 or later. Vendor information also states the issue is fixed in QVR Pro 2.7.4.14 and later; the more specific fixed release cited in the advisory context is 2.7.4.1485.
What products are affected by CVE-2026-22898?
QNAP Systems Qvr Pro.
How severe is CVE-2026-22898?
CVE-2026-22898 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 0.72% (54th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity4Community discussion across Reddit, Mastodon, and other social sources.