dbcve.org
Netvault BackupApplication · Quest

CVE-2026-9782

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 NVBUDeviceDrive 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 NVBUDeviceDrive 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-27633.

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 NVBUDeviceDrive JSON-RPC service allows remote attackers to execute arbitrary code by injecting malicious SQL queries through unsanitized user input. The authentication mechanism can be bypassed, enabling unauthenticated exploitation. Code execution occurs in the context of NETWORK SERVICE.

MitigationApply vendor patch when available; implement parameterized queries or input validation to prevent SQL injection; verify authentication bypass is remediated.

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 Quest NetVault Backup is installed
    Check for NetVault Backup installation by looking for the 'NetVault Backup' service in Windows Services (services.msc) or check for installation directory at C:\Program Files\Quest\NetVault Backup or C:\Program Files (x86)\Quest\NetVault Backup
    Affected if NetVault Backup service or installation directory is found on the system
  2. Determine installed NetVault Backup version
    Locate the NetVault Backup installation directory and look for version information in the main executable (nvmain.exe) or in registry key HKEY_LOCAL_MACHINE\SOFTWARE\Quest\NetVault Backup\CurrentVersion
    Affected if Installed version is less than 14.0.2
  3. Verify if NVBUDeviceDrive service is running
    Open Services (services.msc) and look for 'NetVault Backup Device Drive' service, or run 'sc query NVBUDeviceDrive' from command prompt
    Affected if NVBUDeviceDrive service exists and is running
  4. Check JSON-RPC service exposure
    Review Windows Firewall rules or external network exposure for ports used by NetVault Backup (typically port 8443 for the web interface and JSON-RPC services) using 'netsh firewall show all' or by checking firewall configuration
    Affected if NetVault Backup web/JSON-RPC ports are open to untrusted networks or the internet
  5. Look for signs of exploitation attempts
    Review NetVault Backup logs in the installation directory under 'logs' folder for SQL injection patterns (single quotes, UNION SELECT, xp_cmdshell, or other SQL keywords in request fields) and check for unexpected user accounts or scheduled tasks created under the Network Service account
    Affected if Suspicious SQL patterns found in logs or unauthorized objects created under NETWORK SERVICE context

System is affected if Quest NetVault Backup version is below 14.0.2 and the NVBUDeviceDrive JSON-RPC service is exposed and accessible, allowing potential unauthenticated SQL injection exploitation.

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 vendor patch when available; implement parameterized queries or input validation to prevent SQL injection; verify authentication bypass is remediated.

Recommended fix High confidence

14.0.2

  1. 1. Back up the current NetVault Backup configuration and database before starting the upgrade process
  2. 2. Download NetVault Backup version 14.0.2 (or later) from the Quest Support portal at support.quest.com
  3. 3. Stop the NetVault Backup service on the affected server
  4. 4. Install the NetVault Backup 14.0.2 upgrade following the standard upgrade procedure documented in the Quest installation guide
  5. 5. Verify the upgrade was successful by checking the installed version in the NetVault Backup web interface or CLI
  6. 6. Start the NetVault Backup service
  7. 7. Validate that the NVBUDeviceDrive JSON-RPC functionality is working properly and that the SQL injection vulnerability is resolved
  8. 8. Test backup and restore operations to ensure normal functionality
Caveat Standard minor version upgrade - review Quest release notes for any configuration or feature changes before proceeding

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

Fix this in Netvault Backup Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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