CVE-2026-55513
nebula-mesh is a self-hosted control plane for Slack Nebula mesh …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/forgekeep/nebula-mesh/security/advisories/GHSA-g4x6-jcvr-9m3g
- github.com/forgekeep/nebula-mesh/commit/514006029e09f1991122b86a80e7b25970bcfa98
- github.com/forgekeep/nebula-mesh/releases/tag/v0.5.0
- github.com/advisories/GHSA-g4x6-jcvr-9m3g
- nvd.nist.gov/vuln/detail/CVE-2026-55513
- cve.org/CVERecord?id=CVE-2026-55513
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.