dbcve.org
VelociraptorApplication · Rapid7

CVE-2026-6290

CRITICAL · 9.1 CVSS v3.1 Published 2026-04-15
Fix available
A fix is available. Upgrade to 0.76.3 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Velociraptor versions prior to 0.76.3 contain a vulnerability in the query() plugin which allows access to all orgs with the user's current ACL token. This allows an authenticated GUI user with access in one org, to use the query() plugin, in a notebook cell, to run VQL queries on other orgs which they may not have access to. The user's permissions in the other org are the same as the permissions they have in the org containing the notebook.

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 confidence

Velociraptor versions before 0.76.3 contain an org-scoping vulnerability in the query() plugin where the user's ACL token is not properly restricted to their current organization. This allows an authenticated GUI user with access to one org to run VQL queries against other organizations using their existing permissions, effectively bypassing org boundaries.

MitigationUpgrade Velociraptor to version 0.76.3 or later, which contains the fix for proper organization scoping in the query() plugin.

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
VelociraptorApplication
Affected:< 0.76.3

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
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Check installed Velociraptor version
    Run 'velociraptor --version' on the server or check the version displayed in the GUI footer. Compare the version number to 0.76.3.
    Affected if The installed version is below 0.76.3 (e.g., 0.76.2, 0.76.1, 0.75.x, etc.)
  2. Verify multiple organizations are configured
    Inspect the server configuration file (typically server.config.yaml or via 'velociraptor config show') and look for multiple org definitions under the 'orgs' section.
    Affected if More than one organization is defined in the configuration
  3. Confirm GUI access is enabled
    Check the server configuration for 'GUI' or 'bind_address' settings, and verify the web interface is accessible to users.
    Affected if The GUI is enabled and users can authenticate to it
  4. Check if query() VQL plugin is accessible to users
    Determine if any GUI users have permissions to execute VQL queries through the query() plugin. This is typically controlled by role-based ACLs in the org configuration.
    Affected if Users have VQL query execution permissions in at least one organization

You are affected if you are running Velociraptor versions before 0.76.3, have multiple organizations configured, and allow GUI users to execute VQL queries - the combination of these conditions enables cross-org query execution.

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 0.76.3 or later
Fixed in 0.76.3
Interim mitigation

Upgrade Velociraptor to version 0.76.3 or later, which contains the fix for proper organization scoping in the query() plugin.

Recommended fix High confidence

0.76.3

  1. 1. Back up your current Velociraptor configuration and database
  2. 2. Stop the Velociraptor service
  3. 3. Download Velociraptor version 0.76.3 or later from the official releases
  4. 4. Replace the existing Velociraptor binary with the new version
  5. 5. Verify the upgrade by checking the server version in the GUI (Help -> About)
  6. 6. Restart the Velociraptor service
  7. 7. Test that the query() plugin properly enforces org boundaries by verifying users can only access their own org's data
Caveat Review the 0.76.3 release notes for any breaking changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Velociraptor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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