Forgekeep nebula-mesh
nebula-mesh: Certificate revocation is never enforced at the 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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.7.1
Fixed in 0.7.1
Mitigation
Upgrade nebula-mesh to 0.7.1 or later.
References
- Vendor advisory github.com/forgekeep/nebula-mesh/security/advi…
- Patch github.com/forgekeep/nebula-mesh/commit/0426e2…
- Release notes github.com/forgekeep/nebula-mesh/releases/tag/…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.