CVE-2026-17535

Velociraptor Multiple Crashes in NTFS Parser when applied to invalid NTFS Volumes

Published Aug 11, 2026 CVSS 3.1 · 6.2 Medium EPSS < 1% KEV · Not listed
Description
Velociraptor's NTFS parsing library mishandles several out of bound and memory exhaustion bugs which may be triggered by maliciously crafted NTFS images.

Typically Velociraptor's NTFS parser is used on live NTFS filesystems, limiting the opportunity of attackers corrupting the filesystem. However, in some applications (e.g.  dead disk forensics https://docs.velociraptor.app/docs/forensic/deaddisk/ ) Velociraptor may be used on untrusted NTFS image files. 

If an attacker is able to inject maliciously corrupted NTFS Volumes they can cause a crash and a Denial of Service.

Analysis

AI-generated

Technical impact

Velociraptor’s NTFS parsing library mishandles several out‑of‑bounds accesses and division‑by‑zero conditions that can be triggered by a maliciously crafted NTFS image. The resulting crash or uncontrolled memory allocation leads to a denial of service, and the library’s use of buffer reads without proper bounds checks is indicated by CWE‑125, CWE‑369, and CWE‑789.

Affected Systems

Rapid7 Velociraptor includes the buggy NTFS parser. While the parser is normally used against live filesystems, it is also invoked in forensic modes such as the dead‑disk forensics feature, where untrusted image files can be loaded. No specific product version is listed, so any version containing the affected parser is potentially vulnerable.

Risk and Exploitability

The CVSS score of 6.2 signals a moderate risk. EPSS data is absent and the vulnerability is not listed in the CISA KEV catalog, indicating that no widespread exploitation has been documented. The attack requires that an adversary can supply a malicious NTFS volume to the parser, for example by uploading a crafted image into a forensic workflow or by directly feeding the image to a service that processes disk images. Successful exploitation results in an application crash or memory exhaustion but does not provide code execution or other advanced capabilities.

Remediation

Vendor Workaround

The vulnerability results in a crash or memory exhaustion.


OpenCVE Recommended Actions

  • Upgrade to the latest Velociraptor release that includes the NTFS parser fix, as noted in the vendor’s advisory.
  • Restrict the ability to provide NTFS image files to trusted users or processes; deny this capability in environments where the data source cannot be verified.
  • Before parsing, validate NTFS images using an independent tool or implement additional bounds checks to guard against kernel‑level buffer overflows and division‑by‑zero errors.

Generated by OpenCVE AI on August 11, 2026 at 23:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Rapid7
Rapid7 velociraptor
Vendors & Products Rapid7
Rapid7 velociraptor
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Velociraptor's NTFS parsing library mishandles several out of bound and memory exhaustion bugs which may be triggered by maliciously crafted NTFS images. Typically Velociraptor's NTFS parser is used on live NTFS filesystems, limiting the opportunity of attackers corrupting the filesystem. However, in some applications (e.g.  dead disk forensics https://docs.velociraptor.app/docs/forensic/deaddisk/ ) Velociraptor may be used on untrusted NTFS image files.  If an attacker is able to inject maliciously corrupted NTFS Volumes they can cause a crash and a Denial of Service.
Title Velociraptor Multiple Crashes in NTFS Parser when applied to invalid NTFS Volumes
Weaknesses CWE-125
CWE-369
CWE-789
References
Metrics cvssV3_1

{'score': 6.2, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
rapid7
Published
Updated
Aug 11, 2026, 7:43 PM
Reserved
Jul 27, 2026, 9:21 AM
Status
Awaiting Analysis
Published
Aug 11, 2026, 3:17 PM
Modified
Oct 23, 2026, 7:10 PM