# CVE-2026-78411: Velociraptor Server Metadata update with Insufficient Permission Check

> Attackers with client labeling permissions can modify server-wide configuration metadata, bypassing intended administrative restrictions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-gpw6-25f6-673m

## What is CVE-2026-78411?

CVE-2026-78411 is a medium-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Velociraptor's SetClientMetadata used the wrong permission check to enforce setting metadata on the server. This allows a user with LABEL_CLIENTS permission to update the server metadata.

Server metadata is often used to store site wide configuration data that should only be updated by the server admin.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-78411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78411 is a medium-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78411 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-78411/ (Markdown: https://insights.sbomify.com/CVE-2026-78411/index.md)
```

## Sources

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

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