nebula-mesh: Certificate revocation is never enforced at the mesh
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| forgekeep | nebula-mesh | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Forgekeep | Nebula-mesh |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cm26-5974-52h8 | nebula-mesh: Certificate revocation is never enforced at the mesh |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.446% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Forgekeep
Forgekeep nebula-mesh |
|
| Vendors & Products |
Forgekeep
Forgekeep nebula-mesh |
| 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
|