Vulnerability in github.com/juev/nebula-mesh (CVE-2026-47724)
Summary
Vulnerability in github.com/juev/nebula-mesh (CVE-2026-47724). Successful exploitation can lead to full system takeover. Exploitable via loadAccessibleCA. Mitigation: upgrade to 0.3.4 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-47724 has been found in github.com/juev/nebula-mesh.
Attackers can target a specific entry point like loadAccessibleCA over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/juev/nebula-mesh to 0.3.4 or later.
If unsure, ask your IT team or search "github.com/juev/nebula-mesh CVE-2026-47724" on the vendor's site.
CVE-2026-47724 (github.com/juev/nebula-mesh) — CWE-862 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: loadAccessibleCA / canAccessCA / handleCreateOperatorAPIKey / mintEnrollmentTokenForHost
Patched: 0.3.4 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in github.com/juev/nebula-mesh. Attackers reach the vulnerable code path via loadAccessibleCA.
Check the vendor advisory for the affected versions of github.com/juev/nebula-mesh. Attack surface: loadAccessibleCA / canAccessCA / handleCreateOperatorAPIKey / mintEnrollmentTokenForHost.
Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.
Update to 0.3.4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/juev/nebula-mesh' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/juev/nebula-mesh' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/juev/nebula-meshを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/juev/nebula-mesh to 0.3.4ステージング環境で 0.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com