CVE-2026-47724: nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network

Q: How do I fix CVE-2026-47724?

No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.

Q: Is CVE-2026-47724 being exploited?

CVE-2026-47724 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-47724 affect?

CVE-2026-47724 affects affected software. Severity is critical (CVSS 9.9). nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.4, the `/api/v1/*` route surface trusts the bearer token alone for authorisation on most endpoints. The codebase itself admits th

Q: How urgent is CVE-2026-47724?

Priority 45/100. Critical severity

This month

CRITICAL 9.9

CVE-2026-47724 is a critical-severity flaw (CVSS 9.9) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.4, the `/api/v1/*` route surface trusts the bearer token alone for authorisation on most endpoints. The codebase itself admits this at `internal/api/hosts.go:384`: "API trusts the bearer token for authorisation; per-CA ownership is enforced only in the Web layer." The Web UI gates state-changing routes through `loadAccessibleCA` (`intern

Why this priority

Critical severity

A fixed release or distro patch exists.

Risk facts

CVSS score	9.9 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-07-23
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc.

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Timeline

2026-07-23 21:17 UTCPublished CVE record published
2026-10-24 13:10 UTCUpdated Record last modified

Exact fixes by distribution

Go · github.com/juev/nebula-mesh · FIXED · 0.3.4 · vulnerable: < 0.3.4 · source

go get github.com/juev/nebula-mesh@v0.3.4 go list -m github.com/juev/nebula-mesh

Fedora 46 · gnome-shell-extension-tiling-assistant · FIXED · 56-1.fc46 · FEDORA-2026-ebf66a5321 · source

sudo dnf upgrade --advisory=FEDORA-2026-ebf66a5321

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-47724?

No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.

Is CVE-2026-47724 being exploited?

CVE-2026-47724 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-47724 affect?

CVE-2026-47724 affects affected software. Severity is critical (CVSS 9.9). nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.4, the `/api/v1/*` route surface trusts the bearer token alone for authorisation on most endpoints. The codebase itself admits th

How urgent is CVE-2026-47724?

Priority 45/100. Critical severity

Software pages

Slack vulnerabilities

References

← Back to latest CVEs