forgekeep nebula-mesh up to 0.3.1 internal/api/audit.go handleGetAuditLog information disclosure

Summaryinfo

A vulnerability classified as problematic has been found in forgekeep nebula-mesh up to 0.3.1. Impacted is the function handleGetAuditLog of the file internal/api/audit.go. Performing a manipulation results in information disclosure. This vulnerability is cataloged as CVE-2026-47726. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability classified as problematic has been found in forgekeep nebula-mesh up to 0.3.1. This affects the function handleGetAuditLog of the file internal/api/audit.go. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.2, internal/api/audit.go:12 — handleGetAuditLog does no admin check. The route is bearer-auth gated only; any operator API key returns the full audit log via store.ListAuditEntries (up to limit=1000). This includes cross-tenant actor names, host/CA/operator IDs, action timestamps, and masked-IP entries from rate-limit refusals — enough surface for a tenant to enumerate the server's activity, infer staffing patterns, or identify high-value targets. This issue has been patched in version 0.3.2.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-47726 since 05/19/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

Upgrading to version 0.3.2 eliminates this vulnerability.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• forgekeep

Name

• nebula-mesh

Version

• 0.3.0
• 0.3.1

Website

• Product: https://github.com/forgekeep/nebula-mesh/

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion