dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-47724

CRITICAL · 9.9 CVSS v3.1 Published 2026-07-23
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click Patch available 4 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

nebula-mesh before version 0.3.4 has broken authorization on API endpoints. The `/api/v1/*` routes trust bearer tokens for authorization without verifying per-CA ownership, unlike the Web UI and CA-management endpoints which properly gate access. Combined with the per-operator CA model, any non-admin operator API key can perform cross-tenant access and privilege escalation across host, network, firewall, mobile-bundle, and operator endpoints.

MitigationUpgrade to nebula-mesh version 0.3.4 which implements proper per-CA ownership verification across all API endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if nebula-mesh is installed
    Look for nebula-mesh binary or service (check /usr/local/bin/, /opt/, or running processes with 'ps aux | grep nebula'). Check for configuration files typically in /etc/nebula/ or a config.yaml with 'nebula-mesh' references.
    Affected if nebula-mesh is present in the environment
  2. Determine the installed nebula-mesh version
    Run 'nebula-mesh --version' or check the version from the binary/service file metadata. Compare the version number against the affected range (versions before 0.3.4).
    Affected if The installed version is lower than 0.3.4 (e.g., 0.3.3, 0.3.2, etc.)
  3. Check if API endpoints are exposed
    Inspect the nebula-mesh configuration file for HTTP/HTTPS listener settings under 'api:' or 'http:' sections. Verify if port 8080, 443, or a custom API port is configured and listening.
    Affected if The API service (/api/v1/* endpoints) is exposed and accessible on a network interface
  4. Identify operator API keys in use
    Review the configuration for 'operatorKeys' or 'apiKeys' entries. Check for operator-level keys (non-admin) defined in the CA configuration or secrets management.
    Affected if Non-admin operator API keys are configured and active in the system
  5. Verify authorization gaps on vulnerable endpoints
    If API access is available, attempt a request to one of the unprotected endpoints: /api/v1/host, /api/v1/network, /api/v1/firewall, /api/v1/mobile-bundle, or /api/v1/operator using a non-admin operator key. Check if cross-tenant data is returned without authorization errors.
    Affected if A non-admin operator key can access data from other tenants or perform actions outside their authorized scope

A user is affected if nebula-mesh version is below 0.3.4 AND the API service is exposed with operator API keys configured, allowing unauthorized cross-tenant access through the unprotected endpoints.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to nebula-mesh version 0.3.4 which implements proper per-CA ownership verification across all API endpoints.

Recommended fix High confidence

version 0.3.4

  1. 1. Identify all currently running instances of nebula-mesh
  2. 2. Check the current version of each instance (likely via --version flag or API endpoint)
  3. 3. Upgrade each instance to version 0.3.4 or later
  4. 4. Verify the upgrade was successful by checking the version
  5. 5. Test that authorization is properly enforced on the affected endpoints (host, network, firewall, mobile-bundle, and operator endpoints)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,200
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47724 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data