Quick answers
- Is CVE-2026-19583 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19583 being exploited in the wild.
- How severe is CVE-2026-19583?
- Critical severity, with a CVSS score of 9.9, published 10 September 2026.
- Which products and versions are affected?
- Velocidex Velociraptor prior to 0.77.2.
- Is there a fix for CVE-2026-19583?
- A patch was published on 2026-08-10: Fix merged in PR #4967 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19583 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-19583?
- Check whether you run Velocidex Velociraptor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Velociraptor enforces permission checks on certain high-risk artifacts (e.g., Linux.Sys.BashShell) that require the EXECVE permission to schedule, preventing unauthorized command execution. However, no equivalent permission checks were applied to client monitoring artifacts, and client monitoring artifacts were not required to carry the CLIENT_EVENTS type. An attacker with permission to schedule client monitoring artifacts could therefore bypass the EXECVE permission requirement and schedule restricted artifacts for execution on endpoints. The vulnerability was patched by enforcing required permissions validation on SetClientMonitoringState() operations.
Affected products
- Velocidex Velociraptor prior to 0.77.2
Timeline
- 2026-09-10: disclosed
- 2026-08-10: patched: Fix merged in PR #4967