CVE-2026-6290 is a high severity (CVSS 8.0) authorization flaw in Rapid7 Velociraptor. The query() plugin can run VQL against other orgs using the user's current ACL token. Upgrade to 0.76.3 or 0.75.8, or deny the query plugin. It only matters if you rely on org separation.
What's affected
- Rapid7 Velociraptor 0.76 releases before 0.76.3. Fixed in 0.76.3.
- Velociraptor 0.75 releases before 0.75.8. Fixed in 0.75.8.
- The advisory page also says to update to the latest release, 0.77.3, for multiple CVEs.
- Weakness: CWE-863, incorrect authorization. CVSS 8.0 (high), vector
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H.
The advisory says the flaw lets an authenticated GUI user with access in one org run VQL queries on other orgs, using the plugin in a notebook cell. The user's permissions in the other org match the permissions they hold in the org that contains the notebook.
How to check if you're exposed
Check the server version, then decide whether the issue applies to you.
velociraptor version
The advisory says it matters for deployments that use org separation to contain untrusted users to a subset of orgs. Most users run several orgs for separate environments but give the same trusted group access to all of them. In that case the advisory says it does not apply, because all users already hold the same permissions everywhere.
What to do now
- Check your server version and whether you use multiple orgs.
- List which users can reach only some orgs and review what permissions they hold in each.
- Upgrade to 0.76.3 or 0.75.8, or better, to the latest release the advisory points to.
- If you cannot upgrade, add the query plugin to
denied_pluginsinserver.config.yaml, as the advisory shows.
The advisory's workaround is this configuration:
security:
denied_plugins:
- query
Why it matters
Orgs in Velociraptor separate environments. A permission check that only looks at the org holding the notebook, and then lets a plugin reach other orgs with the same token, breaks that separation. That is CWE-863, incorrect authorization.
The score reflects a high privilege requirement and high complexity, along with a changed scope. For many deployments there is no practical effect, since one group already has access to everything. For managed service or multi tenant setups, the boundary is the whole point. The record's KEV flag is false.
Quick check
Does this affect single org deployments?
Not in any meaningful way. The advisory says it matters when you use org separation to contain untrusted users.
What is the quick workaround?
Deny the query plugin in the server security configuration.
Sources
Last reviewed: 19 October 2026.
