nebula-mesh: Certificate revocation is never enforced at the mesh (CVE-2026-61699) | HOL Guard CVE

High · CVSS 8.1CVE-2026-61699GHSA-CM26-5974-52H8

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

Answer in brief

CVE-2026-61699 records a High severity (CVSS 8.1) vulnerability in nebula-mesh: Certificate revocation is never enforced at the mesh. The current sources do not mark it as known exploited. The current feed maps forgekeep/nebula-mesh (generic), github.com/forgekeep/nebula-mesh (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 4, 2026Updated Sep 8, 2026Source checked Sep 17, 2026First seen by HOL Jul 15, 2026Material review Sep 8, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 8.1
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 8.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps forgekeep/nebula-mesh (generic), github.com/forgekeep/nebula-mesh (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
forgekeep/nebula-meshgeneric	< 0.7.1	Not reported
github.com/forgekeep/nebula-meshgo	<0.7.1	0.7.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for forgekeep/nebula-mesh, github.com/forgekeep/nebula-mesh.
Review the reported fix. Update github.com/forgekeep/nebula-mesh to 0.7.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Jul 15, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.