Summary
Velociraptor contains an authorization enforcement flaw that can let a user with permission to run arbitrary VQL schedule new client collections without the required collection permission.
In affected deployments, an analyst-level user may escalate privileges to investigator-level collection capabilities by running a VQL query that resets the authorization provider.
Affected context
The issue occurs in Velociraptor deployments where:
- Users can execute arbitrary VQL queries, such as through notebooks
- Scheduling a new collection normally requires the
COLLECT_CLIENTpermission - A VQL operation can reset or alter the active authorization provider
- Authorization is not rechecked after that provider state changes
The affected capability is the scheduling of new collections, which is generally intended for users with an investigator role.
Exploit preconditions
- Attack surface: Velociraptor notebooks or another interface that permits arbitrary VQL execution
- Required access: A user account with permission to run the relevant VQL queries, commonly an analyst-level role
- Trigger point: Execution of a VQL query that resets the authorization provider, followed by a collection scheduling action
- Why exploitation is possible: The application does not consistently enforce the
COLLECT_CLIENTpermission after the authorization context is changed
Why this happens
The vulnerability results from incomplete authorization enforcement across a state-changing workflow. A permission check intended to protect collection scheduling can be bypassed when a VQL query resets the authorization provider and the subsequent operation does not revalidate the caller's effective privileges.
This maps to CWE-862: Missing Authorization, because the application performs a sensitive action without reliably verifying that the requesting principal is authorized for that action under the current authorization state.
Potential impact
- An analyst-level user may schedule unauthorized client collections
- Sensitive endpoint data may be collected without the intended investigator privilege
- Collection activity may be used to support further investigation or privacy violations
- Audit records and authorization boundaries could become less trustworthy
- Organizations may experience privilege escalation within Velociraptor
General mitigation guidance
Mitigation generally focuses on enforcing authorization at every sensitive operation, independent of mutable provider state or the interface used to reach the operation.
Common defensive patterns include:
- Revalidating
COLLECT_CLIENTand related permissions immediately before scheduling a collection - Treating authorization-provider changes as security-sensitive state transitions
- Preventing lower-privileged users from resetting or modifying authorization context
- Applying consistent server-side authorization checks to notebook and API workflows
- Following least-privilege role design and separating VQL execution from collection-management privileges
- Recording and reviewing authorization-provider changes and collection scheduling events
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review checks confirming authorization before every sensitive collection operation
- Tests that exercise permission checks before and after authorization-provider state changes
- Review signals involving global authorization state, provider resets, and privileged actions reached through VQL
- Policy enforcement requiring server-side authorization rather than interface-level or role-label checks
- Monitoring for analyst accounts scheduling collections or performing other investigator-only actions
Automated security testing and code review tools may help identify missing authorization checks, but workflow-specific authorization tests remain important.

