CVE-2026-9787
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 NVBULogDaemon Command 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 NVBULogDaemon JSON-RPC messages. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-27625.
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 · high confidenceCommand injection vulnerability in Quest NetVault Backup's NVBULogDaemon JSON-RPC handler. The flaw results from insufficient validation of user-supplied strings before passing them to system calls, allowing arbitrary command execution. Although authentication is required, the authentication mechanism can be bypassed, enabling remote attackers to execute code in SYSTEM context.
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.
-
Identify if NetVault Backup is installedCheck for the NetVault Backup service in Windows Services or look for the installation in common paths such as C:\Program Files\Quest\NetVault Backup or C:\NetVaultBackupAffected if The NetVault Backup service or installation directory is found on the system
-
Determine installed versionRun 'nvtl version' from the NetVault Backup bin directory, or check the About/Version information in the NetVault Backup management console, or check the installed software list in Windows Control PanelAffected if The installed version is lower than 14.0.2 (for example, 14.0.1, 13.x, or earlier)
-
Verify NVBULogDaemon service is runningCheck Windows Services for 'NetVault Backup Log Daemon' service, or run 'sc query NVBULogDaemon' from command prompt, or look for the process nvbuload.exe or nvbuserd.exe in Task ManagerAffected if The NVBULogDaemon service is installed and running
-
Check JSON-RPC interface exposureReview firewall rules and network configuration to determine if the NetVault Backup management port (default 8443) or the NVBULogDaemon service port is exposed to untrusted networks. Check if the JSON-RPC endpoint is accessible from external IPs.Affected if The NetVault Backup management interface or NVBULogDaemon JSON-RPC handler is accessible from untrusted networks or the internet
-
Look for exploitation indicatorsReview NetVault Backup application logs for failed authentication attempts, unusual command executions, or unexpected JSON-RPC calls. Check for new or suspicious user accounts, scheduled tasks, or services created after the software installation.Affected if Logs show unauthenticated or unusual JSON-RPC commands, or SYSTEM-level commands that were not initiated by legitimate administrators
A system is affected if Quest NetVault Backup is installed with a version lower than 14.0.2 and the NVBULogDaemon JSON-RPC interface is network-accessible.
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; if no patch exists, consider network segmentation to restrict access to NetVault Backup services and monitor for exploitation indicators.
NetVault Backup 14.0.2
- Identify the currently installed NetVault Backup version by checking the application or using the NVBULogDaemon version information
- Download NetVault Backup version 14.0.2 or later from the official Quest support portal (support.quest.com)
- Review the upgrade documentation and release notes for NetVault Backup 14.0.2
- Schedule a maintenance window and perform a full backup of the NetVault Backup configuration and database
- Upgrade NetVault Backup to version 14.0.2 following the official upgrade procedure
- After upgrade, verify the NVBULogDaemon service is running correctly
- Confirm the version number reflects 14.0.2 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9787 — 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-9787 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