Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cm26-5974-52h8 | nebula-mesh: Certificate revocation is never enforced at the mesh |
Tue, 08 Sep 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 07 Sep 2026 08:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Forgekeep
Forgekeep nebula-mesh |
|
| Vendors & Products |
Forgekeep
Forgekeep nebula-mesh |
Fri, 04 Sep 2026 20:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | nebula-mesh: Certificate revocation is never enforced at the mesh | |
| Weaknesses | CWE-299 CWE-672 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-09-08T12:59:24.096Z
Reserved: 2026-07-10T18:36:58.851Z
Link: CVE-2026-61699
Updated: 2026-09-08T12:59:18.436Z
Status : Deferred
Published: 2026-09-04T20:17:24.347
Modified: 2026-09-08T21:05:26.920
Link: CVE-2026-61699
No data.
OpenCVE Enrichment
Updated: 2026-09-07T08:25:49Z
Github GHSA