Is CVE-2026-53604 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53604 being exploited in the wild.

How severe is CVE-2026-53604?

High severity, with a CVSS score of 4, published 4 September 2026.

Which products and versions are affected?

Forgekeep Nebula-Mesh <= 0.3.7; github.com/forgekeep/nebula-mesh (Go) <= 0.3.7, SEMVER:introduced=0,fixed=0.3.8.

Is there a fix for CVE-2026-53604?

Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53604 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-53604?

Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53604: forgekeep nebula-mesh cleartext storage of CA private key in memory

Q: Is there a fix for CVE-2026-53604?

Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-53604 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-53604?

Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53604 · Severity: high · CVSS 4 · Published 2026-09-04

A security issue was identified in nebula-mesh, a tool used for managing secure network overlays. When generating mobile configuration bundles through the web interface, the system fails to securely erase the Certificate Authority (CA) private key from memory after use. If an attacker gains access to the server's memory—for example, through a system crash report or memory scraping—they could recover this key and use it to create unauthorized certificates, potentially gaining full access to the secure network.

Technologies: Forgekeep Nebula-Mesh, github.com/forgekeep/nebula-mesh (Go). Vendors: Forgekeep, Go.

Quick answers

Is CVE-2026-53604 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53604 being exploited in the wild.
How severe is CVE-2026-53604?: High severity, with a CVSS score of 4, published 4 September 2026.
Which products and versions are affected?: Forgekeep Nebula-Mesh <= 0.3.7; github.com/forgekeep/nebula-mesh (Go) <= 0.3.7, SEMVER:introduced=0,fixed=0.3.8.
Is there a fix for CVE-2026-53604?: Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53604 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-53604?: Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/forgekeep/nebula-mesh (Go): upgrade to 0.3.8 or later
```
go get github.com/forgekeep/nebula-mesh@v0.3.8
```

Technical details

A vulnerability exists in the `mobilebundle.Build` function where the `*pki.CAManager` containing a decrypted ed25519 CA private key is not wiped upon function return. While the API handler correctly manages this lifecycle, the web handler `renderMobileBundle` does not, leaving the plaintext key on the Go heap until garbage collection occurs. This is particularly prevalent on error paths (e.g., database errors or signing failures). An attacker with the ability to read process memory, such as through core dumps, swap files, or memory-scraping techniques, can recover the CA signing key to mint arbitrary host certificates. The issue is fixed in version 0.3.8 by ensuring `Wipe()` is called on all return paths.

Affected products

forgekeep nebula-mesh <= 0.3.7

Identifiers

CVE-2026-53604
GHSA-2p2f-px33-4vv5
GO-2026-5984

Timeline

2026-06-04: disclosed
2026-06-04: patched: Version 0.3.8 released
2026-07-14: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.