/

CVE-2026-63464

Severity:

HIGH RISK

(7.7)

Server-Side Request Forgery (CWE-918) in Nebula Webhooks

CVE-2026-63464

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-862, CWE-918

Impact:

Unauthorized server-side access to internal network resources

Severity:

HIGH RISK

(7.7)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Nebula Mesh allows a non-admin operator to enable private-address delivery on a webhook subscription they manage. When that subscription is delivered, the server may make requests to loopback, link-local, or other internal addresses, bypassing its SSRF protections.

Affected context

The issue affects nebula-mesh deployments using webhook subscriptions in versions 0.6.0 through before 0.7.2. It becomes risky when a user-role operator can create or update a managed subscription and set the allow_private option without an administrative authorization check. At delivery time, this option causes the dispatcher to use an HTTP client that does not enforce private, loopback, or link-local address protections.

Exploit preconditions

  • Attack surface: Webhook subscription creation or modification through POST or PATCH API endpoints
  • Required access: Authenticated access as a non-admin operator with permission to manage a webhook subscription
  • Trigger point: Delivery of the operator-controlled webhook subscription
  • Why exploitation is possible: The allow_private field is accepted without an admin authorization check and disables the dispatcher's internal-address filtering

Why this happens

The vulnerability results from an authorization failure combined with an unsafe request-routing decision. A low-privilege user can set a security-sensitive option that should be restricted to administrators, and the delivery path trusts that option to select an unguarded HTTP client. This maps primarily to CWE-918: Server-Side Request Forgery, because server-side requests can be directed toward protected addresses, and secondarily to CWE-862: Missing Authorization, because access control is not enforced for the sensitive field.

Potential impact

  • The server may make requests to loopback, link-local, or private network services
  • Attackers could retrieve responses from internal administrative or cloud metadata endpoints
  • Internal services may be probed or abused through the control plane
  • Authentication material or sensitive application data could be exposed
  • Network segmentation assumptions may be weakened

General mitigation guidance

Mitigation generally focuses on enforcing authorization for security-sensitive webhook options and preserving SSRF protections across every request path.

Common defensive patterns include:

  • Restricting private-address delivery controls to explicitly authorized administrative roles
  • Enforcing field-level authorization consistently for create and update operations
  • Using a single guarded HTTP client for webhook delivery, including explicitly approved exceptions
  • Validating resolved destinations against loopback, link-local, private, and other protected ranges
  • Applying network egress controls and least-privilege service permissions
  • Treating webhook targets and delivery options as untrusted input by default

How teams detect issues like this

Organizations can look for:

  • Static analysis and code review findings where user-controlled fields select security-sensitive clients or request policies
  • Missing role or capability checks around fields that disable validation or network restrictions
  • API tests confirming that non-admin roles cannot set protected webhook options
  • Audit events showing changes to allow_private, webhook destinations, or delivery failures involving internal addresses
  • Network monitoring for control-plane requests to loopback, link-local, private, or cloud metadata ranges
  • Policy enforcement that blocks unauthorized egress from the control-plane workload

Sources

SourceLink
github.comgithub.com/forgekeep/nebula-mesh/commit/f3c54530e388dd21763e548923426e60a8e93ff0
github.comgithub.com/forgekeep/nebula-mesh/releases/tag/v0.7.2
github.comgithub.com/forgekeep/nebula-mesh/security/advisories/GHSA-7rx3-5wx3-5v76

Frequently asked

questions

It may be exploitable through the application's API by an authenticated operator who can manage a webhook subscription, subject to deployment and network controls.

No. The described flaw allows a non-admin user-role operator to set the sensitive option on their own managed subscription.

Enforce field-level authorization for private-address delivery settings and ensure every webhook request uses a consistently guarded, allowlisted request path.

Treat webhook destinations and delivery controls as untrusted, test authorization for each security-sensitive field, and combine application-level SSRF defenses with restrictive network egress policies.

Find out what's already
exploitable in your codebase.