|
| 1 | +--- |
| 2 | +menutitle: "CVE-2026-8795" |
| 3 | +title: "CVE-2026-8795 YAML Injection Leading to Potential Analyst Targeting" |
| 4 | +description: | |
| 5 | + A YAML injection vulnerability in the |
| 6 | + Windows.Collectors.Remapping artifact allows an attacker who |
| 7 | + supplies a crafted collection ZIP to execute arbitrary VQL on the |
| 8 | + analyst's machine. |
| 9 | +weight: -10 |
| 10 | +date: 2026-05-01T00:00:00Z |
| 11 | +no_edit: true |
| 12 | +noTitle: false |
| 13 | +no_children: true |
| 14 | +--- |
| 15 | + |
| 16 | +<div class="cve"> |
| 17 | + <p> |
| 18 | + <span>Published |
| 19 | + </span>on 2026-06-04 |
| 20 | + </p> |
| 21 | + <p> |
| 22 | + </p> |
| 23 | + <details class="popup"> |
| 24 | + <summary class="lbl rnd sec CVSS HIGH">CVSS · HIGH · 7.8 |
| 25 | + <sub>⁄10 |
| 26 | + </sub> |
| 27 | + <span style="font-size:0px;opacity:0"> · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| 28 | + </span> |
| 29 | + </summary> |
| 30 | + <div class="pop wht rnd shd pad bor"> |
| 31 | + <span>Scoring scenario: |
| 32 | + </span>GENERAL |
| 33 | + <div>attackVector: |
| 34 | + <b>LOCAL |
| 35 | + </b> |
| 36 | + </div> |
| 37 | + <div>attackComplexity: |
| 38 | + <b>LOW |
| 39 | + </b> |
| 40 | + </div> |
| 41 | + <div>privilegesRequired: |
| 42 | + <b>NONE |
| 43 | + </b> |
| 44 | + </div> |
| 45 | + <div>userInteraction: |
| 46 | + <b>REQUIRED |
| 47 | + </b> |
| 48 | + </div> |
| 49 | + <div>scope: |
| 50 | + <b>UNCHANGED |
| 51 | + </b> |
| 52 | + </div> |
| 53 | + <div>confidentialityImpact: |
| 54 | + <b>HIGH |
| 55 | + </b> |
| 56 | + </div> |
| 57 | + <div>integrityImpact: |
| 58 | + <b>HIGH |
| 59 | + </b> |
| 60 | + </div> |
| 61 | + <div>availabilityImpact: |
| 62 | + <b>HIGH |
| 63 | + </b> |
| 64 | + </div> |
| 65 | + <div> |
| 66 | + <a class="vgi-dial" href="https://www.first.org/cvss/calculator/3.0#CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H" target="_blank">Open CVSS Calc |
| 67 | + </a> |
| 68 | + </div> |
| 69 | + </div> |
| 70 | + </details> |
| 71 | + <p> |
| 72 | + </p> |
| 73 | + <div id="description"> |
| 74 | + <p> |
| 75 | + A YAML injection vulnerability in the Windows.Collectors.Remapping |
| 76 | + artifact allows an attacker who supplies a crafted |
| 77 | + collection ZIP to execute arbitrary VQL on the analyst's |
| 78 | + machine. The hostname field in client_info.json inside the ZIP is |
| 79 | + inserted into a YAML template via Go's text/template without any |
| 80 | + YAML escaping. By embedding a literal " followed by newlines in |
| 81 | + the hostname, an attacker breaks out of the YAML quoted string and |
| 82 | + injects a new mount remapping entry whose scope field contains VQL |
| 83 | + that executes with NullACLManager (all permissions granted, no |
| 84 | + sandboxing) when the analyst applies the generated remapping file |
| 85 | + with --remap. |
| 86 | + </p> |
| 87 | + </div> |
| 88 | + <div id="problem"> |
| 89 | + <h2>Problem: |
| 90 | + </h2> |
| 91 | + <p>CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') |
| 92 | + <a href="https://cwe.mitre.org/data/definitions/74" target="_blank"> |
| 93 | + <small>CWE-74</small> |
| 94 | + </a> |
| 95 | + <br> |
| 96 | + </p> |
| 97 | + <p>CWE-94 Improper Control of Generation of Code ('Code Injection') |
| 98 | + <a href="https://cwe.mitre.org/data/definitions/94" target="_blank"> |
| 99 | + <small>CWE-94</small> |
| 100 | + </a> |
| 101 | + <br> |
| 102 | + </p> |
| 103 | + <p>CWE-116 Improper Encoding or Escaping of Output |
| 104 | + <a href="https://cwe.mitre.org/data/definitions/116" target="_blank"> |
| 105 | + <small>CWE-116</small> |
| 106 | + </a> |
| 107 | + <br> |
| 108 | + </p> |
| 109 | + |
| 110 | + </div> |
| 111 | + <div id="impact"> |
| 112 | + <h2>Impact: |
| 113 | + </h2> |
| 114 | + <p>CAPEC-549: Local Execution of Code |
| 115 | + <a href="https://capec.mitre.org/data/definitions/549.html" target="_blank"> |
| 116 | + <small>CAPEC-549 |
| 117 | + </small> |
| 118 | + </a> |
| 119 | + <br> |
| 120 | + </p> |
| 121 | + </div> |
| 122 | + <div id="status"> |
| 123 | + <h2>Product Status: |
| 124 | + </h2> |
| 125 | + <table class="striped"> |
| 126 | + <colgroup> |
| 127 | + <col> |
| 128 | + <col class="affectedCol"> |
| 129 | + </colgroup> |
| 130 | + <thead> |
| 131 | + <tr> |
| 132 | + <th>Product |
| 133 | + </th> |
| 134 | + <th>Affected |
| 135 | + </th> |
| 136 | + </tr> |
| 137 | + </thead> |
| 138 | + <tbody> |
| 139 | + <tr> |
| 140 | + <td rowspan="1"> |
| 141 | + <b class="vgi-package">Rapid7 Velociraptor |
| 142 | + </b> |
| 143 | + <i> on |
| 144 | + </i> |
| 145 | + <span class="vgi-stack">Linux |
| 146 | + </span> |
| 147 | + <br> |
| 148 | + <a class="vgi-ext" href="https://github.com/Velocidex/velociraptor">source repo |
| 149 | + </a> |
| 150 | + <br> |
| 151 | + <span class="vgi-impact">Default status is unaffected |
| 152 | + </span> |
| 153 | + </td> |
| 154 | + <td> |
| 155 | + before 0.76.6 |
| 156 | + </td> |
| 157 | + </tr> |
| 158 | + </tbody> |
| 159 | + </table> |
| 160 | + <br style="font-size:0;"> |
| 161 | + </div> |
| 162 | + <div class="rnd pad sec vgap" id="credits"> |
| 163 | + <h2>Credits: |
| 164 | + </h2> |
| 165 | + <p>We thank <b>Artificial Intelligence</b> for identifying and reporting this issue responsibly |
| 166 | + </p> |
| 167 | + </div> |
| 168 | + <div id="references"> |
| 169 | + <h2>References |
| 170 | + </h2> |
| 171 | + <p> |
| 172 | + </p> |
| 173 | + <div> |
| 174 | + <a href="https://docs.velociraptor.app/announcements/advisories/cve-2026-8795/">docs.velociraptor.app/announcements/advisories/cve-2026-8795/ |
| 175 | + </a> |
| 176 | + </div> |
| 177 | + <p> |
| 178 | + </p> |
| 179 | + </div> |
| 180 | +</div> |
| 181 | + |
| 182 | +## Required configuration for exposure |
| 183 | + |
| 184 | +This vulnerability only affects users who use |
| 185 | +[remapping](/docs/forensic/deaddisk/creating_running/) to directly |
| 186 | +operate on offline collections. This usage typically uses the |
| 187 | +`Windows.Collectors.Remapping` artifact to generate a remapping file |
| 188 | +and then subsequently uses that remapping file to collect artifacts on |
| 189 | +the offline collector file directly. This is a very niche use case and |
| 190 | +a very common processing pipeline. |
| 191 | + |
| 192 | +To mitigate this issue you can upgrade the server to version |
| 193 | +`0.76.6` or copy the latest [Windows.Collectors.Remapping](https://github.com/Velocidex/velociraptor/blob/master/artifacts/definitions/Windows/Collectors/Remapping.yaml) artifact from the |
| 194 | +latest release into the [config file](/docs/deployment/references/#Frontend.artifact_definitions_directory). |
0 commit comments