# CVE-2026-19583: Velociraptor Required Permissions bypass by using client monitoring queries

> Attackers can bypass permission checks to execute arbitrary commands on endpoints by scheduling restricted artifacts via client monitoring queries.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2026
- **Updated:** 11 Sep 2026
- **Also known as:** GHSA-jfjq-fc5j-227m

## What is CVE-2026-19583?

CVE-2026-19583 is a critical missing authorization vulnerability in Rapid7 Velociraptor, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Velociraptor allows some sensitive artifacts to be gated by additional permissions. For example, the Linux.Sys.BashShell artifact allows arbitrary command execution on endpoints, and so it requires the EXECVE permission to schedule. However, no such check was implemented for client monitoring artifacts. Additionally there was no requirement that client monitoring artifacts carry the CLIENT_EVENTS type. This allows any user who can schedule client monitoring artifacts to also schedule otherwise restricted artifacts (such as Linux.Sys.BashShell).

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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


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

No fix has been published for CVE-2026-19583 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19583 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19583 is a critical missing authorization vulnerability in Rapid7 Velociraptor, published on 10 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19583 in the wild and no public exploit code.

Affected product: Rapid7 Velociraptor. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-19583/ (Markdown: https://insights.sbomify.com/CVE-2026-19583/index.md)
```

## Sources

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

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