CVE-2026-61699

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-71720 (ENISA EUVD) · GHSA-cm26-5974-52h8 (GitHub Security Advisories) · GO-2026-5986 (OSV.dev)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.1Exploit: No code on recordExposed 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.7.1, revocation is the only in-band mechanism that isolates a compromised/offboarded host from a Nebula mesh. Because the blocklist never reaches any peer's config.yml, a Blocked host retains full overlay reachability to every peer under its CA (and internal services on the mesh) for up to 30d (agent) / 365d (mobile). An attacker who exfiltrates host.key+host.crt can run stock slackhq/nebula directly, ignore the agent's 403/410 poll responses, and stay connected after the operator revokes the host. Operator-visible state (UI shows blocked, audit log records it) is misleading. This issue has been patched in version 0.7.1.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (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_release, github, github_commit.
GitHub release Patch Available

v0.7.1

Patch available: forgekeep/nebula-mesh v0.7.1

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

commit 0426e2f224a9 (forgekeep/nebula-mesh)

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

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

Certificate revocation is never enforced at the mesh: nebula-agent drops the polled blocklist and the generated config.yml has no pki.blocklist, so blocked/compromised hosts keep full mesh access until their cert expires (up to 30d agent / 365d mobile) · Advisory · forgekeep/nebula-mesh · GitHub

https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8

Vendor Advisories for CVE-2026-61699(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/forgekeep/nebula-mesh @ 0.7.1 (fixes < 0.7.1)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:50 UTCEchelonGraph re-scored
  2. 2026-11-12 16:50 UTCGHSA enrichmentGHSA-cm26-5974-52h8 · GitHub severity HIGH · GitHub CVSS 8.1
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  4. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  5. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  7. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 39th percentile
  8. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  9. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  11. 2026-11-05 06:06 UTCEchelonGraph re-scored
  12. 2026-11-05 06:06 UTCGHSA enrichmentGHSA-cm26-5974-52h8 · GitHub severity HIGH · GitHub CVSS 8.1
  13. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  14. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  15. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  16. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  17. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-cm26-5974-52h8 · GitHub severity HIGH · GitHub CVSS 8.1
  18. 2026-11-01 07:41 UTCEchelonGraph re-scored
  19. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  20. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  21. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  22. 2026-10-28 19:30 UTCEchelonGraph re-scored
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  25. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 38th percentile
Show 63 more
  1. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  2. 2026-10-25 14:14 UTCEchelonGraph re-scored
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  6. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-10-21 00:01 UTCEchelonGraph re-scored
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  9. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  11. 2026-10-18 03:25 UTCEchelonGraph re-scored
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  14. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-13 13:22 UTCEchelonGraph re-scored
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-10-12 15:50 UTCEchelonGraph re-scored
  20. 2026-10-11 19:34 UTCEchelonGraph re-scored
  21. 2026-10-11 16:49 UTCEchelonGraph re-scored
  22. 2026-10-11 14:11 UTCEchelonGraph re-scored
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  26. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  31. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  32. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  34. 2026-10-01 12:50 UTCEchelonGraph re-scored
  35. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  36. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  37. 2026-09-28 08:51 UTCEchelonGraph re-scored
  38. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  39. 2026-09-24 08:58 UTCEchelonGraph re-scored
  40. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  41. 2026-09-23 03:26 UTCEchelonGraph re-scored
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  44. 2026-09-18 04:49 UTCEchelonGraph re-scored
  45. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  46. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  47. 2026-09-13 23:15 UTCEchelonGraph re-scored
  48. 2026-09-13 07:29 UTCEchelonGraph re-scored
  49. 2026-09-11 21:52 UTCEchelonGraph re-scored
  50. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  51. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  52. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  53. 2026-09-08 16:13 UTCEchelonGraph re-scored
  54. 2026-09-08 13:07 UTCEchelonGraph re-scored
  55. 2026-09-08 01:04 UTCEchelonGraph re-scored
  56. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  57. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.2% · 16th percentile
  58. 2026-09-05 20:55 UTCEchelonGraph re-scored
  59. 2026-09-04 20:30 UTCEchelonGraph re-scored
  60. 2026-07-30 19:02 UTCEchelonGraph re-scored
  61. 2026-07-26 11:41 UTCEchelonGraph re-scored
  62. 2026-07-23 03:21 UTCEchelonGraph re-scored
  63. 2026-07-14 20:56 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-61699?
CVE-2026-61699 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.7.1, revocation is the only in-band mechanism that isolates a compromised/offboarded host from a Nebula mesh. Because the blocklist never reaches any peer's config.yml, a Blocked host retains full overlay…
When was the CVE record for CVE-2026-61699 published?
The CVE record for CVE-2026-61699 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-61699 actively exploited?
CVE-2026-61699 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61699?
CVE-2026-61699 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61699?
A fix for CVE-2026-61699 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61699 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-61699

Explore →

Is Your Infrastructure Affected by CVE-2026-61699?

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