# CVE-2026-6948: Unbounded Memory Allocation in VQLResponse Result-Set Writer

> A compromised client can crash the Velociraptor server by sending crafted messages that cause unbounded memory allocation.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 May 2026
- **Updated:** 19 Jun 2026
- **Also known as:** GHSA-r3xq-q2q6-7vcc

## What is CVE-2026-6948?

CVE-2026-6948 is a medium-severity denial of service vulnerability in Rapid7 Velociraptor, published on 3 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Velociraptor versions prior to 0.76.4 contain a resource exhaustion vulnerability in the server's agent control channel.

This allows a compromised or rogue Velociraptor client to crash the server via out-of-memory (OOM) by sending crafted messages through the normal client communication channel.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-6948?


## How do I fix CVE-2026-6948?

Upgrade to a fixed version.

## Is CVE-2026-6948 being exploited?

There is no known exploitation of CVE-2026-6948 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6948 and fix it if it is affected.

What it is: CVE-2026-6948 is a medium-severity denial of service vulnerability in Rapid7 Velociraptor, published on 3 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6948 in the wild and no public exploit code.

Affected product: Rapid7 Velociraptor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6948/ (Markdown: https://insights.sbomify.com/CVE-2026-6948/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6948
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6948
- OSV: https://osv.dev/vulnerability/CVE-2026-6948

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6948/
Summaries are generated and may contain mistakes; the official description above is the record.