dbcve.org
Netvault BackupApplication · Quest

CVE-2026-9784

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 NVBULibraryPort 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 NVBULibraryPort 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-27631.

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 SQL injection vulnerability in Quest NetVault Backup's NVBULibraryPort JSON-RPC service. The flaw results from improper validation of user-supplied strings before using them in SQL query construction. Although authentication is required, the authentication mechanism can be bypassed, allowing remote attackers to execute arbitrary code in the context of the NETWORK SERVICE account.

MitigationApply vendor-provided patches for Quest NetVault Backup and implement input validation with parameterized queries in the NVBULibraryPort component to remediate the SQL injection flaw.

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. Verify NetVault Backup installation
    Check for the presence of Quest NetVault Backup by looking for its installation directory (commonly at C:\Program Files\Quest\NetVault Backup or /opt/netvault) and the nvbu.exe process
    Affected if NetVault Backup is installed and running
  2. Determine installed version
    Open the NetVault Backup web interface or run 'nvault -version' from the command line, or check the version in the Windows Add/Remove Programs or Linux package manager
    Affected if The version number is less than 14.0.2
  3. Confirm NVBULibraryPort service is exposed
    Check if port 8443 (default NVBULibraryPort HTTPS port) or the configured port is listening. Run 'netstat -an | grep 8443' on Linux or 'netstat -an | findstr 8443' on Windows
    Affected if The NVBULibraryPort service port is listening and accessible over the network
  4. Verify JSON-RPC endpoint accessibility
    Attempt to access the NVBULibraryPort JSON-RPC endpoint via curl or a web browser: https://<server>:8443/nvbu/libraryport - check for HTTP 200 response
    Affected if The JSON-RPC endpoint returns a valid response without proper authentication challenges

Your environment is affected if Quest NetVault Backup is installed with a version lower than 14.0.2 and the NVBULibraryPort JSON-RPC service is accessible on the network.

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-provided patches for Quest NetVault Backup and implement input validation with parameterized queries in the NVBULibraryPort component to remediate the SQL injection flaw.

Recommended fix High confidence

Quest NetVault Backup 14.0.2 or later

  1. Back up the current NetVault Backup configuration and database
  2. Download Quest NetVault Backup version 14.0.2 or later from the official Quest support site (support.quest.com)
  3. Review Quest's official upgrade documentation for NetVault Backup
  4. Apply the upgrade to the NetVault Backup server following the documented upgrade procedure
  5. Verify the upgrade was successful by checking the version and testing core functionality
Caveat Review release notes for any configuration or compatibility 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
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
42.0 hours of engineering $7,320
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,712.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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