dbcve.org
InjectionWeakness · CWE-74

CVE-2026-8795

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A YAML injection vulnerability exists in the Windows.Collectors.Remapping artifact of Rapid7 Velociraptor before version 0.76.6. The hostname field in client_info.json inside a collection ZIP is inserted into a YAML template via Go's text/template without escaping. An attacker providing a crafted collection ZIP can leverage literal double quotes and newlines in the hostname to break out of the YAML quoted string and inject a new mount remapping entry. When an analyst applies the generated remapping file with --remap, arbitrary VQL executes on their machine with NullACLManager (all permissions granted, unsandboxed).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A YAML injection vulnerability exists in Velociraptor's Windows.Collectors.Remoting artifact where the hostname field from client_info.json is inserted into a YAML template without proper escaping. An attacker can craft a collection ZIP with double quotes and newlines in the hostname to break out of YAML string containment and inject arbitrary mount remapping entries. When an analyst applies the generated remapping file via --remap, the injected VQL executes with NullACLManager privileges (unsandboxed, all permissions).

MitigationUpgrade Velociraptor to version 0.76.6 or later which contains the patched artifact with proper hostname escaping in the YAML template. Avoid applying remapping files from untrusted sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Velociraptor version
    Run 'velociraptor --version' or 'velociraptor -V' to determine the version number
    Affected if The version is earlier than 0.6.6 (e.g., 0.6.5, 0.6.4, etc.)
  2. Identify remap file usage
    Search for .yaml or .yml remap files in the system, and check command history or logs for '--remap' flag usage with Velociraptor
    Affected if Any remap files have been applied using the --remap flag, especially from untrusted sources
  3. Inspect remap file content for injection patterns
    Examine any remap YAML files for unescaped double quotes or unexpected newlines within hostname fields, which could indicate YAML injection payloads
    Affected if The remap file contains hostname values with unescaped quotes or newline characters that could break YAML string context
  4. Review client_info.json for suspicious hostnames
    Locate and inspect client_info.json files on the server for hostnames containing quotes, newlines, or VQL-like syntax
    Affected if Any client_info.json contains hostname values with special YAML characters or VQL command fragments

You are affected if Velociraptor version is earlier than 0.6.6 AND any remap files (especially from untrusted sources) have been applied using the --remap flag.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Velociraptor to version 0.76.6 or later which contains the patched artifact with proper hostname escaping in the YAML template. Avoid applying remapping files from untrusted sources.

Recommended fix Moderate confidence

0.76.6

  1. Download Velociraptor version 0.76.6 or later from the official releases at docs.velociraptor.app or the GitHub releases page
  2. Replace the existing Velociraptor binary with the new version
  3. Restart any running Velociraptor services if applicable
  4. Verify the version is 0.76.6 or later by running velociraptor --version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8795 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data