CVE-2026-53604

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (7th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 14, 2026

Last Modified

September 8, 2026

Advisory Details (3)

Auto-updated Sep 4, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

v0.3.8

Patch available: forgekeep/nebula-mesh v0.3.8

https://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.8
GitHub commit

commit 1f1ab9aa8472 (forgekeep/nebula-mesh)

Fix landed in forgekeep/nebula-mesh commit 1f1ab9aa8472 — awaiting tagged release

https://github.com/forgekeep/nebula-mesh/commit/1f1ab9aa8472239763d967e3d50a3cd53a1a79b9
GitHub advisoryMentions a patch (unverified)

CA private key not zeroized on web mobile-bundle error paths · Advisory · forgekeep/nebula-mesh · GitHub

https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-2p2f-px33-4vv5

Vendor Advisories for CVE-2026-53604(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/forgekeep/nebula-mesh—
  • every version up to 0.3.8: fixed in 0.3.8
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 32× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  3. 2026-10-12 15:57 UTCEG score recompute
  4. 2026-10-11 19:40 UTCEG score recompute
  5. 2026-10-11 16:55 UTCEG score recompute
  6. 2026-10-11 14:18 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-01 12:52 UTCEG score recompute
  19. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-09-28 08:52 UTCEG score recompute
  23. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 26 more
  1. 2026-09-24 08:59 UTCEG score recompute
  2. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-09-23 03:27 UTCEG score recompute
  4. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-09-18 04:50 UTCEG score recompute
  6. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-13 23:15 UTCEG score recompute
  9. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-09-13 07:38 UTCEG score recompute
  11. 2026-09-11 21:52 UTCEG score recompute
  12. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-09-08 20:25 UTCEG score recompute
  16. 2026-09-08 01:06 UTCEG score recompute
  17. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-05 20:57 UTCEG score recompute
  20. 2026-09-04 20:30 UTCEG score recompute
  21. 2026-09-04 19:45 UTCEG score recomputeFirst assessed: 7.1 HIGH
  22. 2026-09-04 19:44 UTCMITRE cvelistV5CVSS v3 → 7.1 · CVSS v4 → 7.1
  23. 2026-08-01 22:28 UTCEG score recompute
  24. 2026-07-26 11:42 UTCEG score recompute
  25. 2026-07-23 03:19 UTCEG score recompute
  26. 2026-07-14 20:10 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-53604?
CVE-2026-53604 is a high-severity vulnerability; its CVE record was published on July 14, 2026. 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…
When was the CVE record for CVE-2026-53604 published?
The CVE record for CVE-2026-53604 was published on July 14, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-53604 actively exploited?
CVE-2026-53604 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53604?
CVE-2026-53604 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-53604?
A fix for CVE-2026-53604 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53604 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53604

Explore →

Is Your Infrastructure Affected by CVE-2026-53604?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs