CVE-2026-61699

published 4 Sep 2026 · updated 8 Sep 2026

nebula-mesh: Certificate revocation is never enforced at the mesh

8.1HighCVSS 8.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
forgekeep<0.7.1

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-61699 severity on Zeptric[![CVE-2026-61699](https://zeptric.io/badge/cve/CVE-2026-61699.svg)](https://zeptric.io/cve/CVE-2026-61699)