nebula-mesh: Host advanced overrides allow YAML injection into agent config.yml

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-47722: 0.47% estimated exploitation activity in the next 30 days; percentile 40.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

internal/configgen/generator.go:86,108,119 interpolates the operator-supplied ListenHost and TunDevice fields raw into a text/template that produces the agent's config.yml. internal/web/advanced.go:20-35 accepts both with only strings.TrimSpace — no character or shape validation. Exploit An operator (or attacker with any operator key, given the cross-tenant CRUD advisory) sets advtundevice to: The agent fetches the rendered config on its next signed poll. On config reload, it loads the injected YAML keys: the host self-promotes to lighthouse, attracts mesh traffic, or sets amrelay: true to be selected as a relay. The ListenHost field has the same shape. Affected All released versions prior to v0.3.2. Threat model - Today: operator can compromise their own host's config (trivially allowed if they own the host, but they can also set lighthouse/relay flags that the operator-create form does NOT expose — privilege uplift within their own tenant). - Combined with the critical /api/v1…

Published by the source

8 Jun 2026, 23:08 UTC

Last modified by the source

8 Jun 2026, 23:08 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-7hp6-g3pq-3pc3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47722

Advisory: nebula-mesh: Host advanced overrides allow YAML injection into agent config.yml
IDs: CVE-2026-47722, GHSA-7hp6-g3pq-3pc3
Record: https://patchnext.com/advisories/cve-2026-47722 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/juev/nebula-mesh 0.3.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/juev/nebula-mesh: affected < 0.3.2; fixed in 0.3.2

## Suggested inspection (read-only)
- Go github.com/juev/nebula-mesh: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/juev/nebula-mesh.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7hp6-g3pq-3pc3 (GitHub-reviewed advisory GHSA-7hp6-g3pq-3pc3 lists affected ranges: Go github.com/juev/nebula-mesh >=0 <0.3.2)

Commands are suggestions: review each one before running it.