External risk intelligence

Velociraptor Client Monitoring Artifacts Bypass Permissions

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-19583

Velociraptor is an endpoint visibility and digital forensics tool typically deployed within internal administrative or security operations networks. While it involves client-server communication, it is generally restricted to managed endpoints behind internal controls rather than being exposed as a public-facing internet service.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a vulnerability in Velociraptor, an endpoint visibility and digital forensics tool, that could allow unauthorized users to execute arbitrary commands on systems. The issue arises because certain sensitive commands were not properly restricted by necessary permissions. While the tool is generally used internally, confirmation of its presence and exposure is important.

Sensitive commands were not properly restricted.
Undetected access could lead to system compromise.
Confirm relevance and exposure for security.

Attack Path

How an attacker could exploit the issue

An attacker with the ability to schedule client monitoring artifacts in Velociraptor can bypass permission checks. This allows them to execute sensitive artifacts, such as those enabling arbitrary command execution on Linux endpoints, even if they lack the necessary EXECVE permission for those specific artifacts. This could lead to unauthorized command execution and potential compromise of affected systems.

Requires ability to schedule monitoring artifacts.
Triggers by scheduling restricted artifacts.
Risk of arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, a user who can schedule client monitoring artifacts could potentially execute arbitrary commands on endpoints by bypassing permission checks intended for sensitive artifacts like Linux.Sys.BashShell. This could affect system data and service behavior.

Arbitrary command execution on endpoints.
Unauthenticated users could trigger it.
Compromise of system data and behavior.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in Velociraptor could allow unauthorized command execution on endpoints. Ownership typically falls to the security operations or digital forensics team managing Velociraptor, supported by the infrastructure or platform team responsible for its deployment. The first critical step is to inventory all Velociraptor instances, confirm their reachability and business criticality, and identify the specific owner for each deployment to plan targeted remediation.

Identify Velociraptor deployments and owners.
Verify artifact scheduling and access controls.
Plan remediation based on risk assessment.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is Velociraptor and how is it used?

Velociraptor is a powerful open-source tool designed for endpoint visibility, digital forensics, and incident response. Security teams use it to collect data across large fleets of systems, perform live investigations, and automate complex monitoring tasks. It functions through a client-server architecture where a central server manages agents deployed on endpoints to execute various diagnostic artifacts and scripts.

What does CVE-2026-19583 mean for my software?

This vulnerability is classified as CWE-732, which refers to incorrect permission assignment for critical resources. In the context of CVE-2026-19583, the software failed to enforce required security checks for specific tasks. Because certain restricted actions did not verify if the user possessed the necessary permissions, they could be executed inappropriately, bypassing intended access controls within the platform.

How can an attacker trigger this vulnerability?

An attacker needs the ability to schedule client monitoring artifacts within the Velociraptor environment to exploit this flaw. The bug is triggered when a user schedules a restricted artifact without the system validating their credentials against required security permissions. Simply using standard, unrestricted monitoring features does not trigger this issue; it specifically occurs when restricted operations are invoked without the proper authorization check.

Is my Velociraptor deployment at risk?

Halo Surface Signal suggests that risk is unlikely for most users because Velociraptor is typically deployed within internal, protected administrative networks rather than as a public-facing internet service. While the vulnerability exists in the software logic, the practical danger is significantly lower if your deployment is restricted to internal infrastructure behind standard security controls.

What should I do if I run Velociraptor?

The first step is to locate all Velociraptor instances across your environment to understand your footprint. Once identified, determine who owns and manages each deployment. Verify the current access control configurations for artifact scheduling to ensure that users have only the minimum necessary privileges. Use this inventory to prepare for official software updates or configuration patches from the vendor.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.