dbcve.org
VelociraptorApplication · Rapid7

CVE-2026-7572

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-06
Fix available
A fix is available. Upgrade to 0.76.5 or later.
See remediation →
58/100
Remediation priority · Elevated
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
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.

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

An off-by-one error (CWE-193) exists in the ConsumeUnit16Array and ConsumeUnit64Array functions in Velociraptor before 0.76.5. When parsing specially crafted .evtx (Windows Event Log) files through the parse_evtx VQL plugin, the boundary check incorrectly allows reading one unit beyond the allocated buffer, causing a process crash and resulting in Denial of Service.

MitigationUpgrade Velociraptor to version 0.76.5 or later. As a defensive measure, restrict access to the parse_evtx VQL plugin to trusted users and avoid processing untrusted .evtx files until the upgrade is applied.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VelociraptorApplication
Affected:< 0.76.5

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Velociraptor installed version
    Run 'velociraptor --version' or check the binary metadata to determine the installed version number
    Affected if The version is lower than 0.76.5 (e.g., 0.76.4, 0.76.0, etc.)
  2. Identify parse_evtx plugin usage
    Search VQL query logs, hunt configurations, or artifact definitions for 'parse_evtx' or 'parse_evtx()' function calls
    Affected if The parse_evtx plugin is actively used or enabled in any VQL queries or artifacts
  3. Review .evtx file processing workflows
    Audit any automated or manual workflows that process Windows Event Log (.evtx) files through Velociraptor
    Affected if Your environment processes .evtx files via the parse_evtx plugin from untrusted or external sources
  4. Check VQL plugin access controls
    Inspect Velociraptor server or client configuration for ACLs or restrictions on the parse_evtx plugin usage
    Affected if No restrictions exist on who can execute parse_evtx queries and the version is vulnerable

You are affected if Velociraptor version is below 0.76.5 AND the parse_evtx plugin is being used to process .evtx files from any source that could supply a maliciously crafted file.

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
Upgrade available Upgrade to 0.76.5 or later
Fixed in 0.76.5
Interim mitigation

Upgrade Velociraptor to version 0.76.5 or later. As a defensive measure, restrict access to the parse_evtx VQL plugin to trusted users and avoid processing untrusted .evtx files until the upgrade is applied.

Recommended fix Moderate confidence

0.76.5

  1. 1. Navigate to the official Velociraptor releases page (https://github.com/Velocidex/velociraptor/releases) or the official documentation site (docs.velociraptor.app)
  2. 2. Download Velociraptor version 0.76.5 or later for your operating system (Windows or Linux)
  3. 3. Verify the checksum of the downloaded binary against the published checksums
  4. 4. Stop any running Velociraptor services
  5. 5. Replace the existing Velociraptor binary with the new version
  6. 6. Restart the Velociraptor service
  7. 7. Test that the parse_evtx VQL plugin functions correctly with .evtx files

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

Fix this in Velociraptor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7572 — 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-7572 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