CVE-2026-7572 json
Velociraptor EVTX Parser — Process Crash via Crafted .evtx File
published 6mo ago modified 3mo ago also GHSA-6cmp-qv2f-x97x , GO-2026-5174 , EUVD-2026-27516
- cvss
- 4.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 3%
- public exploits
- 0
- none known
Summary
An off-by-one error (CWE-193) in the ConsumeUnit16Array and ConsumeUnit64Array functions in Velocidex Velociraptor before version 0.76.5 on Windows and Linux allows a local attacker to cause a Denial of Service (DoS) via a process crash by providing a specially crafted .evtx file to the parse_evtx VQL plugin.
Patch / fix
- go www.velocidex.com/golang/velociraptor 0.76.5
- Velocidex velociraptor 0.76.5
- velociraptor openSUSE Tumbleweed 0.76.7.0.git145.b60ef1146-1.1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:12070-1openSUSE-SU-2026:21483-1
Is CVE-2026-7572 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6mo ago
Exploit prediction
0.14% chance of exploitation in the next 30 days, higher than 3% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 4.4 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | www.velocidex.com/golang/velociraptor | <0.76.5 all versions |
0.76.5 |
Affected products
- Velocidex velociraptor
Classification
- Weakness
-
- CWE-193 Off-by-one Error
References
Sources
- CVE List CVE-2026-7572
- GitHub Advisory GHSA-6cmp-qv2f-x97x
- NVD CVE-2026-7572
- OSV GO-2026-5174
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.