Vulnerability · Published Jul 23, 2026 · Assigned by GitHub_M
CVE-2026-47724nebula-mesh: API endpoints lack ownership checks, enabling cross-operator privilege escalation
Critical 9.9
In plain English
A critical-severity missing authorization in nebula-mesh from juev. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 42% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.4, the `/api/v1/*` route surface trusts the bearer token alone for authorisation on most endpoints. The codebase itself admits this at `internal/api/hosts.go:384`: "API trusts the bearer token for authorisation; per-CA ownership is enforced only in the Web layer." The Web UI gates state-changing routes through `loadAccessibleCA` (`internal/web/cas.go`); CA-management endpoints in `internal/api/cas.go` ALSO have proper `canAccessCA` gates. The gap is on the host, network, firewall, mobile-bundle, and most operator endpoints. Combined with the per-operator CA model from ADR 0002, this gives any non-admin operator API key broad cross-tenant access — instant privilege escalation in the worst case. Version 0.3.4 fixes the issue.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Go | github.com/juev/nebula-mesh | 0.3.4 | GHSA-598g-h2vc-h5vg |
| Go | github.com/juev/nebula-mesh | 0.3.4 | GO-2026-5139 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| juev | nebula-mesh | < 0.3.4 |
Weakness: CWE-862 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H