dbcve.org
Netvault BackupApplication · Quest

CVE-2026-9781

HIGH · 8.8 CVSS v3.0 Published 2026-06-25
Fix available
A fix is available. Upgrade to 14.0.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click 8 weeks old

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
Quest NetVault Backup NVBURASDevice SQL Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Quest NetVault Backup. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the processing of NVBURASDevice JSON-RPC messages. The issue results from the lack of proper validation of a user-supplied string before using it to construct SQL queries. An attacker can leverage this vulnerability to execute code in the context of NETWORK SERVICE. Was ZDI-CAN-27648.

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

SQL injection vulnerability in Quest NetVault Backup's NVBURASDevice JSON-RPC message processing allows remote attackers to execute arbitrary code. The flaw stems from improper validation of user-supplied strings before constructing SQL queries. Although authentication is required, the authentication mechanism can be bypassed, enabling code execution in NETWORK SERVICE context.

MitigationApply the vendor patch or update to a fixed version of Quest NetVault Backup. If no patch is available, restrict network access to the NetVault Backup service and implement additional input validation or a WAF as a compensating control.

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
Netvault BackupApplication
Affected:< 14.0.2

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

CVSS:3.0/AV:N/AC:L/PR:L/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. Identify if NetVault Backup is installed
    Check for the presence of NetVault Backup by looking for its installation directory (commonly at C:\Program Files\Quest\NetVault Backup or C:\NetVault) or check Windows Services for 'NetVault Backup Service'
    Affected if The software is present on the system
  2. Determine the installed version
    Check the NetVault Backup version by inspecting the binary or registry. Common paths: look for 'nvadmin.exe' or check HKLM\SOFTWARE\Quest\NetVault Backup\CurrentVersion in Windows Registry
    Affected if The installed version is below 14.0.2
  3. Verify if JSON-RPC interface is accessible
    NetVault Backup exposes JSON-RPC on port 8443 (HTTPS) or 20031 (HTTP). Attempt a local or remote HTTP request to the NVBURASDevice endpoint, e.g., GET http://localhost:20031/NVBURASDevice or check if port 20031/8443 is listening
    Affected if The JSON-RPC service is listening and reachable (even locally)
  4. Check if authentication bypass is possible
    Per the CVE, authentication can be bypassed. This is a condition of the vulnerability rather than a configuration to verify; if the service is exposed, the vulnerability applies
    Affected if The JSON-RPC interface is exposed to any network caller (local or remote)

If NetVault Backup is installed with a version below 14.0.2 AND the JSON-RPC service (port 20031 or 8443) is accessible, the system is vulnerable to CVE-2026-9781.

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 14.0.2 or later
Fixed in 14.0.2
Interim mitigation

Apply the vendor patch or update to a fixed version of Quest NetVault Backup. If no patch is available, restrict network access to the NetVault Backup service and implement additional input validation or a WAF as a compensating control.

Recommended fix High confidence

14.0.2

  1. Obtain NetVault Backup version 14.0.2 or later from Quest support portal (support.quest.com)
  2. Back up the current NetVault Backup configuration and database
  3. Stop the NetVault Backup services before upgrading
  4. Install NetVault Backup version 14.0.2 or latest stable release
  5. Verify the upgrade was successful by checking the installed version in the management console
  6. Restart NetVault Backup services
Caveat Review Quest release notes for any configuration or feature changes between your current version and 14.0.2

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

Fix this in Netvault Backup Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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