CVE-2026-7572 — velociraptor
MEDIUMCVE-2026-7572 is a medium-severity (CVSS 4.4) CWE-193 vulnerability in www.velocidex.com/golang/velociraptor. A fix is available for www.velocidex.com/golang/velociraptor — see the affected versions and patch details below.
Velocidex Velociraptor has an off-by-one error
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-7572.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
www.velocidex.com/golang/velociraptorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | www.velocidex.com/golang/velociraptor | all versions | 0.76.5go get www.velocidex.com/golang/velociraptor@v0.76.5 |
Affected Products
velociraptorrapid7Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for www.velocidex.com/golang/velociraptor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update www.velocidex.com/golang/velociraptor to 0.76.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-7572 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is CVE-2026-7572 in your dependencies?
Find it across Go, including transitive dependencies.