# CVE-2026-18860: Velociraptor incorrect Org deletion permissions check

> Child org admins can delete other orgs due to incorrect permission checks, allowing unauthorized data modification and security bypass.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/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:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-jm4c-88wp-rfjq

## What is CVE-2026-18860?

CVE-2026-18860 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Velociraptor allows multi-tenant deployments named "Orgs".

By default Velociraptor, uses the ROOT org, but users can create child orgs for other tenants within the same deployment.

Users can have different permissions in each org. To manage Orgs, Velociraptor usually examines the ORG_ADMIN permission on the ROOT org.

This issue results from the Velociraptor server allowing for the deletion of Orgs by incorrectly checking the ORG_ADMIN permission of callers within the calling ORG instead of the ROOT org. However, Org admins of child orgs were able to add this permission to their ACL token within their own org. This allows an administrator in a child org, which is not also an administrator in the ROOT org, to delete other orgs.

Weakness: CWE-280 (Improper Handling of Insufficient Permissions or Privileges)

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


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

Apply the vendor's patch.

## Is CVE-2026-18860 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18860 is a high-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 11 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18860 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-18860/ (Markdown: https://insights.sbomify.com/CVE-2026-18860/index.md)
```

## Sources

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

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