CVE-2026-53604
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-212 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2020-1940 | High | 7.5 | 4.5% | - | - |
| CVE-2022-29900 | Medium | 6.5 | 3.8% | - | Fix |
| CVE-2002-0704 | High | 7.5 | 3.2% | - | - |
| CVE-2020-15094 | High | 8.0 | 3.0% | - | Fix |
| CVE-2022-23633 | High | 7.4 | 2.2% | - | Fix |
| CVE-2019-19362 | Medium | 6.5 | 2.1% | - | - |
Common questions
How do I fix CVE-2026-53604?
No published fix for CVE-2026-53604 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-53604 being actively exploited?
Not that we know of. CVE-2026-53604 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.12% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2026-53604?
CVE-2026-53604 has a CVSS v4 base score of 7.1, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-53604
Markdown
[](https://tridentstack.com/cve/CVE-2026-53604)HTML
<a href="https://tridentstack.com/cve/CVE-2026-53604"><img src="https://tridentstack.com/cve/badge/CVE-2026-53604.svg" alt="CVE-2026-53604"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-08.