CVE-2026-47724: CWE-862: Missing Authorization in juev nebula-mesh
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.
AI Analysis
Technical Summary
The juev nebula-mesh control plane for Slack Nebula mesh VPN versions before 0.3.4 improperly authorize API requests by trusting bearer tokens alone on most `/api/v1/*` endpoints. While the Web UI and CA-management endpoints enforce per-CA ownership checks, host, network, firewall, mobile-bundle, and operator endpoints do not. This authorization gap enables non-admin operator API keys to access resources across tenants, causing privilege escalation. Version 0.3.4 addresses this by correcting authorization enforcement.
Potential Impact
An attacker with a non-admin operator API key can bypass intended authorization boundaries, gaining unauthorized access to host, network, firewall, mobile-bundle, and operator endpoints across multiple tenants. This leads to privilege escalation with full confidentiality, integrity, and availability impact as indicated by the CVSS 9.9 score.
Mitigation Recommendations
Upgrade to juev nebula-mesh version 0.3.4 or later, where the authorization issue is fixed. Patch status is not explicitly stated but the fix is included in version 0.3.4. Until upgrading, restrict API key distribution and monitor for unauthorized access.
CVE-2026-47724: CWE-862: Missing Authorization in juev nebula-mesh
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.
CVSS v3.1
Score 9.9critical
Affected software
pkg:github/forgekeep/nebula-meshRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The juev nebula-mesh control plane for Slack Nebula mesh VPN versions before 0.3.4 improperly authorize API requests by trusting bearer tokens alone on most `/api/v1/*` endpoints. While the Web UI and CA-management endpoints enforce per-CA ownership checks, host, network, firewall, mobile-bundle, and operator endpoints do not. This authorization gap enables non-admin operator API keys to access resources across tenants, causing privilege escalation. Version 0.3.4 addresses this by correcting authorization enforcement.
Potential Impact
An attacker with a non-admin operator API key can bypass intended authorization boundaries, gaining unauthorized access to host, network, firewall, mobile-bundle, and operator endpoints across multiple tenants. This leads to privilege escalation with full confidentiality, integrity, and availability impact as indicated by the CVSS 9.9 score.
Mitigation Recommendations
Upgrade to juev nebula-mesh version 0.3.4 or later, where the authorization issue is fixed. Patch status is not explicitly stated but the fix is included in version 0.3.4. Until upgrading, restrict API key distribution and monitor for unauthorized access.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:29:25.482Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a62806b9c2644c7f8b34ba5
Added to database: 07/23/2026, 20:58:19 UTC
Last enriched: 07/30/2026, 22:11:59 UTC
Last updated: 09/05/2026, 10:52:10 UTC
Views: 92
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.