Quick answers
- Is CVE-2026-78412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-78412 being exploited in the wild.
- How severe is CVE-2026-78412?
- Medium severity, with a CVSS score of 4.9, published 5 October 2026.
- Which products and versions are affected?
- Velociraptor before 0.77.3.
- Is there a fix for CVE-2026-78412?
- Yes: fixed in 0.77.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-78412 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-78412?
- Check whether you run Velociraptor at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.77.3
Technical details
The WatchEvent gRPC API accepts an OrgId parameter specifying which organization's events to stream, but the server validates the caller's permissions against their own organization rather than the requested organization. An authenticated attacker can specify a different OrgId to read events from organizations for which they lack authorization, bypassing the intended multi-tenant isolation.
Affected products
- Velociraptor Velociraptor before 0.77.3
Timeline
- 2026-10-05: disclosed