Is CVE-2026-47726 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-47726 being exploited in the wild.

How severe is CVE-2026-47726?

High severity, with a CVSS score of 4, published 28 July 2026.

Which products and versions are affected?

github.com/juev/nebula-mesh (Go) <= 0.3.1, SEMVER:introduced=0,fixed=0.3.2.

Is there a fix for CVE-2026-47726?

Yes. github.com/juev/nebula-mesh (Go): upgrade to 0.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-47726 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-47726?

Check whether you run github.com/juev/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47726: juev nebula-mesh improper authorization in audit log endpoint

Q: Is there a fix for CVE-2026-47726?

Yes. github.com/juev/nebula-mesh (Go): upgrade to 0.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-47726 attacked?

It is attacked over the network, in a hosted service.

Q: Am I affected by CVE-2026-47726?

Check whether you run github.com/juev/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-47726 · Severity: high · CVSS 4 · Published 2026-07-28

Nebula-mesh is a control plane for managing Slack Nebula virtual private networks. A security flaw allowed any registered user with an API key to view the entire system's audit logs, which are normally restricted to administrators. This could allow unauthorized users to see sensitive activity across the entire network, including staffing patterns and the identities of high-value targets.

Technologies: github.com/juev/nebula-mesh (Go). Vendors: Go.

Quick answers

Is CVE-2026-47726 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-47726 being exploited in the wild.
How severe is CVE-2026-47726?: High severity, with a CVSS score of 4, published 28 July 2026.
Which products and versions are affected?: github.com/juev/nebula-mesh (Go) <= 0.3.1, SEMVER:introduced=0,fixed=0.3.2.
Is there a fix for CVE-2026-47726?: Yes. github.com/juev/nebula-mesh (Go): upgrade to 0.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-47726 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-47726?: Check whether you run github.com/juev/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/juev/nebula-mesh (Go): upgrade to 0.3.2 or later
```
go get github.com/juev/nebula-mesh@v0.3.2
```

Technical details

An improper authorization vulnerability (CWE-285) exists in the `handleGetAuditLog` function within `internal/api/audit.go`. The endpoint was protected only by a bearer-auth gate, meaning any valid operator API key could retrieve up to 1,000 audit entries via `store.ListAuditEntries`. These logs contain sensitive metadata including cross-tenant actor names, host/CA/operator IDs, and action timestamps. An attacker with low-privileged access could use this information to enumerate server activity and identify high-value targets. The issue is resolved in version 0.3.2 by implementing an `actorIsAdmin` check on the affected route.

Affected products

juev nebula-mesh < 0.3.2

Identifiers

CVE-2026-47726
GHSA-qm33-p5p9-f8vg
GO-2026-5586

Timeline

2026-05-20: patched: Fix committed to repository
2026-05-21: advisory: GitHub Security Advisory published
2026-07-28: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.