CVE-2025-6264: Rapid7 Velociraptor · Incorrect Default Permissions
Affects Rapid7 VelociraptorSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 1.0% chance of exploitation in 30 days – higher than 63% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 20 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rapid7 Velociraptor | Affected
| Fixed in– |
AI-suggested
1. Immediately audit and restrict the assignment of the COLLECT_CLIENT permission and Investigator role within Velociraptor to only trusted personnel with a clear operational need. 2. Implement strict role-based access controls (RBAC) and regularly review artifact permissions to ensure sensitive artifacts like Admin.Client.UpdateClientConfig require EXECVE or equivalent high-level permissions. 3. Monitor Velociraptor logs and endpoint activity for unusual artifact collection or configuration update attempts, especially from Investigator accounts. 4. Employ network segmentation and endpoint protection measures to limit the impact of potential endpoint takeovers. 5. Coordinate with Rapid7 to obtain and apply patches or configuration updates addressing this vulnerability as soon as they become available. 6. Consider additional multi-factor authentication (MFA) for users with elevated Velociraptor permissions to reduce risk of credential compromise. 7. Conduct regular security awareness training emphasizing the risks of privilege misuse within endpoint monitoring tools. 8. Where possible, implement anomaly detection to flag unexpected changes in client configurations or artifact usage patterns. These steps go beyond generic advice by focusing on permission hygiene, monitoring, and proactive detection tailored to Velociraptor’s operational context.
Description
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).