CVE-2026-61699
nebula-mesh is a self-hosted control plane for Slack Nebula mesh …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8
- github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb
- github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1
- github.com/advisories/GHSA-cm26-5974-52h8
- nvd.nist.gov/vuln/detail/CVE-2026-61699
- cve.org/CVERecord?id=CVE-2026-61699
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.