What’s Vulnerable › Vulnerabilities

CVE-2026-61699: nebula-mesh: Certificate revocation is never enforced at the mesh

• Severity: high (CVSS 8.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-04 · updated 2026-09-08
• Weakness: CWE-299

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.

Affected products

• forgekeep nebula-mesh: before 0.7.1

References

• https://github.com/forgekeep/nebula-mesh/commit/0426e2f224a9b1e2029029bf923c93ed39d21cdb
• https://github.com/forgekeep/nebula-mesh/releases/tag/v0.7.1
• https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8
• https://github.com/forgekeep/nebula-mesh/security/advisories/GHSA-cm26-5974-52h8

Get alerted when CVE-2026-61699 or the next vulnerability affects your stack