CVE-2026-19583: Rapid7 Velociraptor · Incorrect Permission Assignment for Critical Resource
Affects Rapid7 VelociraptorSource CVE Database V5
Not known to be exploited · CVSS 9.9 Critical · fixed in 0.77.2 : patch Rapid7 Velociraptor as a priority.
Data as of 10/25/2026, 09:03:59 UTC
- Exploitation
Not in CISA KEV, no exploitation reported
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.77.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:LWhat to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rapid7Velociraptor | Affected
| Fixed in
|
GitHubVelociraptorpkg:github/VelociraptorOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Velociraptor version 0.77.2 and later. Users should upgrade to version 0.77.2 or newer to remediate this vulnerability. No additional mitigation steps are indicated in the vendor advisory.
Description
CVE-2026-19583 is a critical vulnerability in Rapid7 Velociraptor versions before 0.77.2 involving incorrect permission assignment for sensitive artifacts. Specifically, client monitoring artifacts lacked proper permission checks, allowing users with scheduling rights for these artifacts to also schedule highly privileged artifacts like Linux.Sys.BashShell, which enables arbitrary command execution on endpoints. This flaw could lead to unauthorized privilege escalation and control over affected systems.
Impact
An attacker with the ability to schedule client monitoring artifacts can escalate privileges to execute arbitrary commands on endpoints, potentially leading to full system compromise. The vulnerability has a CVSS 3.1 score of 9.9, indicating critical severity with high confidentiality, integrity, and low availability impact. There are no known exploits in the wild at this time.
Summary
The vulnerability arises because Velociraptor does not enforce the EXECVE permission requirement on client monitoring artifacts, nor does it require these artifacts to carry the CLIENT_EVENTS type. Consequently, any user able to schedule client monitoring artifacts can bypass intended restrictions and schedule artifacts that should require elevated permissions, such as Linux.Sys.BashShell. This incorrect permission assignment (CWE-732) compromises the security model of artifact scheduling in Velociraptor.
Weaknesses
- CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.