# CVE-2026-78412: WatchEvent API streams another organization's live events

> Attackers with API access in one organization can read live events from other organizations due to incorrect permission checks.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** GHSA-83qj-9c78-grhx

## What is CVE-2026-78412?

CVE-2026-78412 is a medium-severity missing authorization vulnerability in Rapid7 Velociraptor, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Velociraptor's WatchEvent gRPC API can specify the OrgId of the org from which events should be streamed. The server checks the API permissions against the caller's Org instead of the requested Org. This allows a user with API access in one org to read events from another org for which they have no access.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-78412 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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