CVE-2026-9786
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 · uneditedQuest NetVault Backup NVBUDashboard 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 NVBUDashboard 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-27626.
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 confidenceQuest NetVault Backup's NVBUDashboard component fails to validate user-supplied strings before using them in SQL query construction. An attacker can bypass authentication and inject malicious SQL via JSON-RPC messages, ultimately achieving remote code execution as the NETWORK SERVICE account.
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< 14.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Quest NetVault Backup installationCheck for the presence of NetVault Backup by looking for the installation directory (typically C:\Program Files\Quest\NetVault Backup or /opt/quest/netvault) and the 'NetVault Backup Service' in Windows Services or the netvault process on Linux.Affected if NetVault Backup is installed on the system.
-
Identify installed versionOn Windows, check the version in Control Panel > Programs and Features > NetVault Backup, or inspect the binary version info of the main executable (typically nvmanager.exe or similar in the installation bin folder). On Linux, run 'netvault version' or check /opt/quest/netvault/config/nv.config for version information.Affected if The installed version is any release prior to 14.0.2.
-
Verify NVBUDashboard component statusCheck if the NVBUDashboard web interface is enabled and accessible. Look for the 'Dashboard' or 'NVBUDashboard' service in the NetVault Backup service configuration, or attempt to access the web portal (default ports 2010, 8443, or 80/443 for the dashboard).Affected if The NVBUDashboard web interface is exposed and accessible on the network.
-
Review authentication configurationExamine the NetVault Backup authentication settings in the web console under Administration > Security or in the configuration files (typically nvauth.xml or security.cfg in the config directory). Verify whether authentication can be bypassed for the dashboard endpoints.Affected if Authentication for the dashboard is misconfigured or can be bypassed.
If NetVault Backup versions prior to 14.0.2 are installed with the NVBUDashboard component exposed, the environment is likely vulnerable to SQL injection and potential remote code execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped14.0.2
Apply vendor patch when available; implement strict input validation and parameterized queries to neutralize SQL injection vectors; verify authentication mechanisms cannot be bypassed.
NetVault Backup 14.0.2
- Navigate to the Quest Software support portal at support.quest.com
- Locate the NetVault Backup product downloads section
- Download NetVault Backup version 14.0.2 or later
- Review the upgrade documentation and release notes for version 14.0.2
- Execute the installer on the NetVault Backup server, following the on-screen prompts
- Verify the upgrade was successful by checking the NetVault Backup version in the administration console
- Confirm that the NVBUDashboard service is running properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9786 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9786 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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