Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-8h84-fhqq-q58v | nebula-mesh: Decrypted CA private key persists in heap after signing |
Tue, 28 Jul 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Juev
Juev nebula-mesh |
|
| Vendors & Products |
Juev
Juev nebula-mesh |
Tue, 28 Jul 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | nebula-mesh: Decrypted CA private key persists in heap after signing | |
| Weaknesses | CWE-244 | |
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-07-28T17:40:37.329Z
Reserved: 2026-05-20T17:44:09.587Z
Link: CVE-2026-48025
No data.
No data.
No data.
OpenCVE Enrichment
Updated: 2026-07-28T20:15:03Z
-
CWE-244
Improper Clearing of Heap Memory Before Release ('Heap Inspection')
Github GHSA