# CVE-2026-19200: Velociraptor Analyst overwrites live built-in artifacts through verify()

> An analyst can overwrite live built-in artifacts via the verify() function, bypassing permission checks and potentially escalating privileges or modifying system behavior.

- **Severity:** High 8.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-jj5c-prr4-v82g

## What is CVE-2026-19200?

CVE-2026-19200 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 24 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The Velociraptor verify() VQL function allows a user to verify an artifact for syntatic and other issues. Due to an implementation fault in this VQL function, the global artifact repository is used which allows callers to overwrite existing artifacts without the required permissions.  The attacker need only have the NOTEBOOK_EDIT permission (e.g. an analyst role) to be able to call this function.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-862 (Missing Authorization)

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


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

No fix has been published for CVE-2026-19200 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-19200 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19200 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 24 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19200 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-19200/ (Markdown: https://insights.sbomify.com/CVE-2026-19200/index.md)
```

## Sources

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

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