Rapid7 Velociraptor’s Windows.Collectors.Remapping artifact had a YAML injection flaw that allowed an attacker to insert malicious YAML content into a collection ZIP’s client_info.json hostname field. The Go text/template engine rendered the hostname without escaping, so the attacker could break out of a quoted string and inject a new mount remapping entry. When an analyst applies the malicious remapping file with the --remap option, the embedded VQL code is executed under the NullACLManager, granting the attacker unrestricted control over the analyst’s machine.

This issue affects Rapid7 Velociraptor deployments running before version 0.76.6 on Windows systems that use the Remapping artifact for mount configuration. Only the Windows.Collectors.Remapping component is vulnerable; sysadmins must verify their cluster membership configuration and the version of Velociraptor in use.

The vulnerability has a CVSS score of 7.8, indicating high severity, but its EPSS score is not available, so current exploitation probability is unclear. It is not yet listed in the CISA KEV catalog, suggesting no confirmed public exploitation. The likely attack vector requires an attacker to supply a malicious collection ZIP to a user who will run the remap command, meaning the threat is primarily to a trusted analyst’s environment, yet the impact would be equivalent to local privilege escalation on that host.