/

CVE-2026-64954

Severity:

HIGH RISK

(8.2)

Authorization Bypass (CWE-862) in Velociraptor VQL Queries

CVE-2026-64954

Awaiting Analysis

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Privilege Escalation and Unauthorized Client Collection

Severity:

HIGH RISK

(8.2)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

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_CLIENT permission
  • 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_CLIENT permission 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_CLIENT and 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.

Sources

SourceLink
docs.velociraptor.appdocs.velociraptor.app/announcements/advisories/cve-2026-64954/
github.comgithub.com/Velocidex/velociraptor/commit/d7de958e846d3742a7a3a8538fd463e4f12fc528

Frequently asked

questions

Exploitability depends on deployment architecture and exposed interfaces. It can be reached through Velociraptor functionality that allows an authenticated user to execute arbitrary VQL, including notebook-based workflows.

The attacker generally needs an account that can run the relevant arbitrary VQL queries. An analyst-level account may be sufficient; direct investigator privileges should not be required.

Enforce the required collection permissions on the server immediately before scheduling each collection, and do not rely on authorization state that can be reset or modified by the requesting user.

Use centralized, fail-closed authorization checks, restrict access to authorization-provider controls, test privilege boundaries across all interfaces, and monitor for lower-privileged users invoking investigator-only actions.

Find out what's already
exploitable in your codebase.