CVE Alert: CVE-2025-6264 – Rapid7 – Velociraptor
CVE-2025-6264
Velociraptor allows collection of VQL queries packaged into Artifacts from endpoints. These artifacts can be used to do anything and usually run with elevated permissions. To limit access to some dangerous artifact, Velociraptor allows for those to require high permissions like EXECVE to launch. The Admin.Client.UpdateClientConfig is an artifact used to update the client’s configuration. This artifact did not enforce an additional required permission, allowing users with COLLECT_CLIENT permissions (normally given by the "Investigator" role) to collect it from endpoints and update the configuration. This can lead to arbitrary command execution and endpoint takeover. To successfully exploit this vulnerability the user must already have access to collect artifacts from the endpoint (i.e. have the COLLECT_CLIENT given typically by the "Investigator’ role).
AI Summary Analysis
**Risk verdict** High risk: exploitation is actively present, requiring urgent remediation.
**Why this matters** Velociraptor artifacts can run with elevated permissions, and this flaw allows users with COLLECT_CLIENT rights to harvest artifacts and update configuration without a strengthened permission check. Successful exploitation can yield arbitrary command execution and endpoint takeover, enabling ransomware deployment, persistence, or data exfiltration across managed hosts.
**Most likely attack path** An attacker who already possesses COLLECT_CLIENT (Investigator) access can trigger the problematic Admin.Client.UpdateClientConfig artifact to alter client settings. The attack is network-accessible but bounded by the need for prior privileged access; once triggered, commands may execute with elevated rights, and Scope is CHANGED, permitting broader impact beyond the initial host.
**Who is most exposed** Environments deploying Velociraptor with investigator-level artifact permissions or lax RBAC are most at risk, particularly where centralized artifact management or broad artifact visibility exists.
Detection ideas
- Unusual or elevated use of UpdateClientConfig artifact by non-admins
- Artifacts collection events from Investigator roles outside normal maintenance windows
- Unexpected or privileged commands executed on endpoints
- Configuration changes without corresponding admin actions
- Anomalous asset behaviour following artifact collection
Mitigation and prioritisation
- Apply fixed release (0.74.3+) and follow vendor advisories
- Enforce strict RBAC to limit COLLECT_CLIENT access; restrict UpdateClientConfig usage
- Enable artifact verifier and promote basic artifacts to reduce risky operations
- Implement least privilege for artifact execution and require elevated approvals for config changes
- Plan patch deployment in staging first; monitor for suspicious artifact activity during rollout
A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.
If you like the site, please support us on “Patreon” or “Buy Me A Coffee” using the buttons below
To keep up to date follow us on the below channels.
