# CVE-2026-6290: Velociraptor Query() Plugin Misapplies Permissions To Orgs

> Authenticated users can access data in other organizations via the query plugin, bypassing intended organizational isolation controls.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-hv5g-26jg-pc45, GO-2026-5438

## What is CVE-2026-6290?

CVE-2026-6290 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 15 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-6290?

3 open source packages ship an affected version, including www.velocidex.com/golang/velociraptor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `www.velocidex.com/golang/velociraptor` | Go | All versions | None |
| `www.velocidex.com/golang/velociraptor` | Go | All versions to 0.76.2 | None |
| `www.velocidex.com/golang/velociraptor` | Go | All versions to 0.76.2 | None |

Products: Rapid7 Velociraptor.

## How do I fix CVE-2026-6290?

Upgrade to a fixed version.

## Is CVE-2026-6290 being exploited?

There is no known exploitation of CVE-2026-6290 in the wild and no public exploit code.

## Other vulnerabilities in Rapid7 Velociraptor

- [CVE-2023-0242](https://insights.sbomify.com/CVE-2023-0242/): Insufficient permission check in the VQL copy() function (high 8.8)
- [CVE-2023-5950](https://insights.sbomify.com/CVE-2023-5950/): Rapid7 Velociraptor Reflected XSS (high 8.6)
- [CVE-2026-5329](https://insights.sbomify.com/CVE-2026-5329/): Rapid7 Velociraptor Improper Input Validation in Client Message Handler (high 8.5)
- [CVE-2025-14728](https://insights.sbomify.com/CVE-2025-14728/): Rapid7 Velociraptor Directory Traversal Vulnerability (medium 6.8)
- [CVE-2022-35630](https://insights.sbomify.com/CVE-2022-35630/): Unsafe HTML Injection in Artifact Collection Report (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6290 and fix it if it is affected.

What it is: CVE-2026-6290 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 15 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6290 in the wild and no public exploit code.

Affected packages and fixed versions:
- www.velocidex.com/golang/velociraptor (Go): affected all versions; no fix listed
- www.velocidex.com/golang/velociraptor (Go): affected all versions up to 0.76.2; no fix listed
- www.velocidex.com/golang/velociraptor (Go): affected all versions up to 0.76.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6290/ (Markdown: https://insights.sbomify.com/CVE-2026-6290/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6290
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6290
- OSV: https://osv.dev/vulnerability/CVE-2026-6290

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6290/
Summaries are generated and may contain mistakes; the official description above is the record.