Skip to main content
VulnerabilityPublished

CVE-2026-47726: juev nebula-mesh · Improper Authorization

Affects juev nebula-meshSource CVE Database V5

0

Not known to be exploited · CVSS 7.1 High : upgrade to 0.3.2 soon.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.3.2
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade juev nebula-mesh to 0.3.2.

Affected software

ProductAffectedFixed in
juevnebula-meshAffected
  • <0.3.2
Fixed in
  • 0.3.2

AI-suggested

A fix for this vulnerability is available in juev nebula-mesh version 0.3.2. Users should upgrade to version 0.3.2 or later to ensure proper administrative authorization checks are enforced on the audit log endpoint. No other mitigation guidance is provided or necessary as the issue is resolved by this update.

Description

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.

References

Community reviews

Loading reviews…