fixnx
criticalCVE-2026-47724

CVE-2026-47724 nebula-mesh vulnerability

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` (`internal/web/cas.go`); CA-management endpoints in `internal/api/cas.go` ALSO have proper `canAccessCA` gates. The gap is on the host, network, firewall, mobile-bundle, and most operator endpoints. Combined with the per-operator CA model from ADR 0002, this gives any non-admin operator API key broad cross-tenant access — instant privilege escalation in the worst case. Version 0.3.4 fixes the issue.

Browse Network Security security risks
Productnebula-mesh
CVSS9.9
EPSSNot scored yet
UpdatedJuly 24, 2026

Quick answer

juev nebula-mesh should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • < 0.3.4

Fixed versions

  • Apply the latest vendor-supported patched version.

How to fix it

CVE-2026-47724 affects nebula-mesh and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade nebula-mesh to 0.3.4 or a later vendor-supported fixed release.

  1. Inventory every deployment, device, package, plugin, container, build, and environment that uses nebula-mesh.
  2. Compare the installed version with the recorded affected range: < 0.3.4.
  3. Upgrade nebula-mesh to 0.3.4 or a later vendor-supported fixed release.
  4. Until patched, restrict the affected API or workflow to trusted administrators and enforce an additional access-control layer at the proxy or network boundary.
  5. Review configuration, roles, tokens, network paths, and exposed endpoints connected to nebula-mesh; remove access that is not required.
  6. Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
  7. If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-47724 in place.
  • Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
  • Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
  • Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
  • Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.

Related categories

Network SecurityAPI SecurityAuthorization BypassPrivilege Escalation

Related security risks

More published guidance from the same primary category.

critical

CVE-2026-15704 Eclipse BaSyx Go Components vulnerability

Updated July 24, 2026

medium

CVE-2026-56742 cilium vulnerability

Updated July 19, 2026

medium

Fense Proxy & VPN Blocker <= 3.0.1 - Missing Authorization to Unauthenticated Plugin Option/Transient Deletion via fense_bpvt_save_settings AJAX Action

Updated July 19, 2026

Trusted references

Source advisoryNVDSource advisoryNVDSource advisoryNVD

FAQ

What is affected by CVE-2026-47724?

juev nebula-mesh versions listed as affected should be reviewed: < 0.3.4.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.