forgekeep nebula-mesh up to 0.3.6 PKI ca.go Sign missing encryption

Summaryinfo

A vulnerability labeled as problematic has been found in forgekeep nebula-mesh up to 0.3.6. This affects the function Sign of the file internal/pki/resolver.go/internal/pki/ca.go of the component PKI. The manipulation results in missing encryption. This vulnerability is identified as CVE-2026-48025. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in forgekeep nebula-mesh up to 0.3.6. It has been classified as problematic. Affected is the function Sign of the file internal/pki/resolver.go/internal/pki/ca.go of the component PKI. The manipulation with an unknown input leads to a missing encryption vulnerability. CWE is classifying the issue as CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. This is going to have an impact on confidentiality. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is traded as CVE-2026-48025 since 05/20/2026. The exploitability is told to be difficult. It is possible to launch the attack remotely. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1600 by the MITRE ATT&CK project.

Upgrading to version 0.3.7 eliminates this vulnerability.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• forgekeep

Name

• nebula-mesh

Version

• 0.3.0
• 0.3.1
• 0.3.2
• 0.3.3
• 0.3.4
• 0.3.5
• 0.3.6

Website

• Product: https://github.com/forgekeep/nebula-mesh/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion