CVE-2026-5329
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 · uneditedRapid7 Velociraptor versions prior to 0.76.2 contain an improper input validation vulnerability in the client monitoring message handler on the Velociraptor server (primarily Linux) that allows an authenticated remote attacker to write to arbitrary internal server queues via a crafted monitoring message with a malicious queue name. The server handler that receives client monitoring messages does not sufficiently validate the queue name supplied by the client, allowing a rogue client to write arbitrary messages to privileged internal queues. This may lead to remote code execution on the Velociraptor server. Rapid7 Hosted Velociraptor instances are not affected by this vulnerability.
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 confidenceVelociraptor versions prior to 0.76.2 have an improper input validation vulnerability in the server's client monitoring message handler. An authenticated remote attacker can send crafted monitoring messages with malicious queue names to write to arbitrary internal server queues, potentially achieving remote code execution on the Velociraptor server.
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<= 0.75.6>= 0.76, < 0.76.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
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.
-
Check if Velociraptor is installedLook for the Velociraptor binary (velociraptor or velociraptor.exe) in common locations such as /usr/local/bin, /opt, or C:\Program Files. On Linux/macOS, run 'which velociraptor'. On Windows, check Program Files directories.Affected if Velociraptor binary is found on the system
-
Determine the installed versionRun 'velociraptor --version' from the command line to retrieve the version number.Affected if Version is lower than 0.76.3 or falls within 0.76.0-0.76.2 inclusive (meaning less than 0.76.3)
-
Identify if this is a server deploymentDetermine if the Velociraptor instance is configured as a server (for example, by checking for server configuration files like server.config.yaml or by inspecting running processes for server roles). The vulnerability exists in the server component.Affected if Velociraptor is deployed as a server with client monitoring capabilities
-
Check if client monitoring is enabledInspect the server configuration for client monitoring settings. Look for monitoring-related stanzas in the configuration file (commonly server.config.yaml or similar) that handle client monitoring message queues.Affected if Client monitoring is enabled and the server processes monitoring messages from clients
-
Verify server network exposureDetermine if the Velociraptor server is network-accessible to untrusted clients. The attack requires an authenticated remote attacker to send crafted monitoring messages.Affected if The Velociraptor server accepts connections from clients or users beyond the trusted internal network
You are affected if Velociraptor server version is less than 0.76.3, the server component is running, and client monitoring is enabled with network exposure to potential attackers.
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 · scoped0.76.3
Upgrade Velociraptor to version 0.76.2 or later. Rapid7 Hosted Velociraptor instances are not affected.
0.76.3 or later
- 1. Identify the currently installed Velociraptor version by checking the server or using 'velociraptor --version'
- 2. For Velociraptor <= 0.75.6: Upgrade directly to version 0.76.3 or later
- 3. For Velociraptor >= 0.76.0 and < 0.76.3: Upgrade to version 0.76.3 or later
- 4. Download the appropriate package for your platform from the official Velociraptor releases (docs.velociraptor.app or github.com/Velocidex/velociraptor)
- 5. Follow the standard Velociraptor upgrade procedure: stop the service, replace binaries, then restart the service
- 6. Verify the upgrade was successful by checking the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5329 — 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-5329 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