CVE-2026-48025 is a medium-severity security vulnerability in github.com/juev/nebula-mesh (go), affecting versions < 0.3.7. It is fixed in 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/mobilebundle.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. Affected All released versions up to v0.3.6. Threat model Memory-read access: core dump, ptrace, kernel swap to disk, container/VM snapshot, OOM-debug bundle, side-channel via shared cache lines. Not a remote-network vulnerability, but defeats the master-key + envelope-encryption design's promise of "private key never lingers". Suggested fix Add a Wipe() method on CAManager: At each call site (enroll.go:116, updates.go:297, mobilebundle.go:40, and any new caller), defer caMgr.Wipe() immediately after the Resolve() call. Pattern mirrors the existing defer keystore.Zeroize(dek) discipline in the keystore package. Optional follow-up: wrap m.Sign() to zeroize after each call, removing the contract on callers, but the defer pattern is sufficient as a minimum.
go
github.com/juev/nebula-mesh (< 0.3.7)github.com/forgekeep/nebula-mesh (< 0.3.7)github.com/juev/nebula-mesh → 0.3.7 (go)github.com/forgekeep/nebula-mesh → 0.3.7 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-48025 is reachable in your applications. Explore open-source security for your team.
See if CVE-2026-48025 is reachable in your applications. Get a demo
Already deployed Kodem? See CVE-2026-48025 in your environment →Upgrade the following packages to resolve this vulnerability:
github.com/juev/nebula-mesh to 0.3.7 or latergithub.com/forgekeep/nebula-mesh to 0.3.7 or laterKodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-48025 is a medium-severity security vulnerability in github.com/juev/nebula-mesh (go), affecting versions < 0.3.7. It is fixed in 0.3.7.
github.com/juev/nebula-mesh (go) (versions < 0.3.7)github.com/forgekeep/nebula-mesh (go) (versions < 0.3.7)Yes. CVE-2026-48025 is fixed in 0.3.7. Upgrade to this version or later.
Whether CVE-2026-48025 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
github.com/juev/nebula-mesh to 0.3.7 or latergithub.com/forgekeep/nebula-mesh to 0.3.7 or later