---
id: CVE-2026-53604
title: nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN
summary: >-
  nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to
  version 0.3.8, the web handler renderMobileBundle passes the real
  *pki.CAResolver directly into mobilebundle.Build. Inside Build,
  resolver.LoadByID decrypts t…
severity: high
cvss: 7.1
cvssVector: 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N'
cwe:
  - CWE-212
  - CWE-316
vendor: forgekeep
product: nebula-mesh
affected:
  - nebula-mesh < 0.3.8
patched:
  - github.com/forgekeep/nebula-mesh 0.3.8
published: '2026-09-04'
updated: '2026-09-08'
sourceUpdated: '2026-09-08T21:05:26.920'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-53604'
references:
  - url: >-
      https://github.com/forgekeep/nebula-mesh/commit/1f1ab9aa8472239763d967e3d50a3cd53a1a79b9
    label: security-advisories@github.com
  - url: 'https://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.8'
    label: security-advisories@github.com
  - url: >-
      https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-2p2f-px33-4vv5
    label: security-advisories@github.com
  - url: 'https://github.com/advisories/GHSA-2p2f-px33-4vv5'
tags:
  - nvd
  - cve.org
  - ghsa
  - go
epss: 0.00116
epssPercentile: 0.01838
aliases:
  - GHSA-2p2f-px33-4vv5
ecosystem: go
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-08T16:37:19.531370Z'
cvssSource: cna
ingestedAt: '2026-07-14T20:39:11.246Z'
---

## Overview

nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. Prior to version 0.3.8, the web handler renderMobileBundle passes the real *pki.CAResolver directly into mobilebundle.Build. Inside Build, resolver.LoadByID decrypts the CA's ed25519 private key into a *pki.CAManager, but Build never calls CAManager.Wipe() on any return path. As a result, when a mobile-bundle request goes through the web UI and Build returns — especially on error (missing network, invalid prefix, DB error, signing failure) — the plaintext CA private key remains on the Go heap, unwiped, until garbage collection. An attacker able to read process memory (core dump, swap, memory-scraping) can recover the CA signing key, which would allow minting arbitrary host certificates for the mesh. The API handler already does this correctly: it loads the CAManager, defer caMgr.Wipe(), and wraps it in caManagerResolver. Only the web path is affected. This issue has been patched in version 0.3.8.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

## Package advisory (CVE-2026-53604)

Affected packages:

- `github.com/forgekeep/nebula-mesh <= 0.3.7`

Patched in:

- `github.com/forgekeep/nebula-mesh 0.3.8`

Source: https://github.com/advisories/GHSA-2p2f-px33-4vv5