CVE-2026-47724: critical vulnerability in juev nebula-mesh
nebula-mesh: API endpoints lack ownership checks, enabling cross-operator privilege escalation
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.9epss 0.5%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Affected products
juev · nebula-meshRelated CVEs — juev nebula-mesh
In the same product, most dangerous first.
CVE-2026-47723HIGHnebula-mesh: Web UI and API responses lack security headers (CSP, X-Frame-Options, HSTS, etc.)EPSS 0.5%CVE-2026-48025MEDIUMnebula-mesh: Decrypted CA private key persists in heap after signingEPSS 0.5%CVE-2026-49258HIGHNebula Mesh: Web UI lacks ownership checks, enabling cross-operator access to hosts and networks (read, block, delete)EPSS 0.5%CVE-2026-47722HIGHnebula-mesh: Host advanced overrides allow YAML injection into agent config.ymlEPSS 0.5%CVE-2026-47726HIGHnebula-mesh: GET /api/v1/audit-log discloses all entries to any operatorEPSS 0.3%CVE-2026-48058MEDIUMnebula-mesh: Session and OIDC state cookies lack the Secure attributeEPSS 0.2%