CVE-2026-48025

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

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
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

June 10, 2026

Last Modified

July 30, 2026

Advisory Details (3)

Auto-updated Jul 28, 2026
Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v0.3.7

Patch available: forgekeep/nebula-mesh v0.3.7

https://github.com/forgekeep/nebula-mesh/releases/tag/v0.3.7
github_commit

commit bca1d5914fba (forgekeep/nebula-mesh)

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

https://github.com/forgekeep/nebula-mesh/commit/bca1d5914fbaf3517d3b86145a802c00de4a8122
github Patch Available

Decrypted CA private key persists in heap after signing · Advisory · forgekeep/nebula-mesh · GitHub

https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-8h84-fhqq-q58v

Vendor Advisories for CVE-2026-48025(1)

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

Affected Packages

(2 across 1 ecosystem)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/forgekeep/nebula-mesh—0.3.7—
github.com/juev/nebula-mesh—0.3.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 49× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-23 10:46 UTCEG score recompute
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-21 15:19 UTCEG score recompute
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 17:16 UTCEG score recompute
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 14:56 UTCEG score recompute
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 23:33 UTCEG score recompute
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 23:56 UTCEG score recompute
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-14 03:20 UTCEG score recompute
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 05:18 UTCEG score recompute
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-12 07:13 UTCEG score recompute
  21. 2026-08-11 08:20 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 10:15 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 12:13 UTCEG score recompute
Show 29 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 14:10 UTCEG score recompute
  3. 2026-08-06 18:03 UTCEG score recompute
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-05 20:00 UTCEG score recompute
  6. 2026-08-05 19:17 UTCEPSS rescore
  7. 2026-08-04 15:54 UTCEG score recompute
  8. 2026-08-04 15:10 UTCEPSS rescore
  9. 2026-08-04 10:39 UTCEPSS rescore
  10. 2026-08-03 14:50 UTCEG score recompute
  11. 2026-08-03 10:36 UTCEPSS rescore
  12. 2026-08-02 11:04 UTCEG score recompute
  13. 2026-08-02 02:27 UTCEPSS rescore
  14. 2026-08-01 13:01 UTCEG score recompute
  15. 2026-08-01 04:16 UTCEPSS rescore
  16. 2026-07-30 16:47 UTCEG score recompute
  17. 2026-07-30 16:28 UTCEPSS rescore
  18. 2026-07-30 01:30 UTCEPSS rescore
  19. 2026-07-29 14:20 UTCEG score recompute
  20. 2026-07-29 13:59 UTCEG score recompute
  21. 2026-07-28 18:27 UTCEG score recompute
  22. 2026-07-28 17:54 UTCEG score recompute▲ 6.90
  23. 2026-07-28 17:53 UTCMITRE cvelistV5CVSS v3 → 6.9 · CVSS v4 → 6.9
  24. 2026-07-26 20:58 UTCEG score recompute
  25. 2026-07-23 03:18 UTCEG score recompute
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-13 23:00 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-10 19:17 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-48025?
CVE-2026-48025 is a medium vulnerability published on June 10, 2026. 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…
When was CVE-2026-48025 disclosed?
CVE-2026-48025 was first published in the National Vulnerability Database on June 10, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48025 actively exploited?
CVE-2026-48025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.2% of all scored CVEs.
What is the CVSS score of CVE-2026-48025?
CVE-2026-48025 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-48025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48025, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48025?

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

Start Free Scan →Browse All CVEs