Vulnerability in github.com/juev/nebula-mesh (CVE-2026-48025)
Summary
Vulnerability in github.com/juev/nebula-mesh (CVE-2026-48025). Risk of unauthorized operations or information disclosure. Exploitable via CAManager. Mitigation: upgrade to 0.3.7 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.7, internal/pki/resolver.go:36-64 constructs a CAManager with the plaintext ed25519.PrivateKey after unwrapping via the master key; internal/pki/ca.go:13-16 stores it. Callers at internal/api/enroll.go:116, internal/api/updates.go:297, and internal/api/mobile_bundle.go:40 use the manager for one Sign() and drop the reference on function return — but the underlying slice contents are not wiped before release. The keystore package's contract (internal/keystore/keystore.go doc: "Callers MUST zeroise the returned plaintext DEK as soon as it is no longer needed") is not met by the CAManager consumer. Decrypted CA private keys persist in process heap until Go's GC scavenges the underlying slice — minutes to hours under load, indefinitely on idle servers. This issue has been patched in version 0.3.7.
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-48025 has been found in github.com/juev/nebula-mesh.
Attackers can target a specific entry point like CAManager over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/juev/nebula-mesh to 0.3.7 or later.
If unsure, ask your IT team or search "github.com/juev/nebula-mesh CVE-2026-48025" on the vendor's site.
CVE-2026-48025 (github.com/juev/nebula-mesh) — CWE-244
Attack surface: CAManager / ed25519.PrivateKey / defer
Patched: 0.3.7 — 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-244) exists in github.com/juev/nebula-mesh. Attackers reach the vulnerable code path via CAManager.
Check the vendor advisory for the affected versions of github.com/juev/nebula-mesh. Attack surface: CAManager / ed25519.PrivateKey / defer.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.3.7.
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.7ステージング環境で 0.3.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
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
- web github.com