Answer in brief
CVE-2026-55513 records a Medium severity (CVSS 5.4) vulnerability in nebula-mesh: Web UI host creation ignores configured enrollment token TTL and mints 24-hour bearer enrollment tokens. The current sources do not mark it as known exploited. The current feed maps forgekeep/nebula-mesh (generic), github.com/forgekeep/nebula-mesh (go), github.com/forgekeep/nebula-mesh (go), github.com/forgekeep/nebula-mesh (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. 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.
The current feed maps forgekeep/nebula-mesh (generic), github.com/forgekeep/nebula-mesh (go), github.com/forgekeep/nebula-mesh (go), github.com/forgekeep/nebula-mesh (go) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| forgekeep/nebula-meshgeneric | >= 0.3.0, < 0.5.0 | Not reported |
| github.com/forgekeep/nebula-meshgo | >=0.3.0,<0.5.0 | 0.5.0 |
| github.com/forgekeep/nebula-meshgo | >=0.4.0 <0.5.0 | 0.5.0 |
| github.com/forgekeep/nebula-meshgo | >=0.3.0 <0.5.0 | 0.5.0 |
| github.com/juev/nebula-meshgo | >=0.3.0 | Not reported |
Published upstream
Sep 4, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 8, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
nebula-mesh is a self-hosted control plane for Slack Nebula mesh VPN. From version 0.3.0 to before version 0.5.0, the nebula-mgmt Web UI host-creation path ignores both the server-wide enrollment_token_ttl security setting and per-network network_config.enrollment_token_ttl overrides. API host creation and token-regeneration paths use the configured TTL resolver, but POST /ui/hosts hardcodes now.Add(24 * time.Hour) for newly minted agent enrollment tokens. In deployments that intentionally reduce enrollment-token lifetime, any authenticated operator who can create a host through the Web UI can still mint a bearer enrollment token valid for about 24 hours. This issue has been patched in version 0.5.0.
Quoted source text, attributed separately from HOL analysis.