Server crash via unbounded VQLResponse allocation
Published May 3, 2026 · Updated May 4, 2026
Resource exhaustion in Rapid7 Velociraptor before 0.76.4 allows remote authenticated users to crash Linux servers via agent messages. The VQLResponse result-set writer accepts crafted client messages and allocates memory for their contents without an enforced resource limit. Control of an enrolled or rogue client is required; repeated messages exhaust server memory and terminate the service without reported data disclosure or modification.
Summary
What happened
Resource exhaustion in Rapid7 Velociraptor before 0.76.4 allows remote authenticated users to crash Linux servers via agent messages. The VQLResponse result-set writer accepts crafted client messages and allocates memory for their contents without an enforced resource limit. Control of an enrolled or rogue client is required; repeated messages exhaust server memory and terminate the service without reported data disclosure or modification.
The record
- CVE
- CVE-2026-6948
- Published
- May 3, 2026
- Updated
- May 4, 2026
- Vendor
- Rapid7
- Product
- Velociraptor
- Classifications
- CWE-770, CAPEC-130, T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 3, 2026CVE publishedPublication date reported by the CVE source.
- May 4, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.75.9
- Affected versionversion=0 <0.76.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo