# CVE-2026-47722: nebula-mesh: Host advanced overrides allow YAML injection into agent config.yml

> An attacker can inject YAML into agent configurations via unvalidated host fields, potentially leading to code execution on managed nodes.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jul 2026
- **Updated:** 24 Jul 2026
- **Also known as:** GHSA-7hp6-g3pq-3pc3, GO-2026-5223

## What is CVE-2026-47722?

CVE-2026-47722 is a high-severity code injection vulnerability in juev nebula-mesh, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

nebula-mesh is a self-hosted control plane for Slack Nebula mesh virtual private network. Prior to version 0.3.2, `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. Version 0.3.2 fixes the issue.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-47722?

3 open source packages ship an affected version, including github.com/juev/nebula-mesh.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/juev/nebula-mesh` | Go | All versions | 0.3.2 |
| `github.com/juev/nebula-mesh` | Go | All versions | 0.3.2 |
| `github.com/juev/nebula-mesh` | Go | All versions | 0.3.2 |

## How do I fix CVE-2026-47722?

Upgrade github.com/juev/nebula-mesh to 0.3.2 or later.

## Is CVE-2026-47722 being exploited?

There is no known exploitation of CVE-2026-47722 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47722 and fix it if it is affected.

What it is: CVE-2026-47722 is a high-severity code injection vulnerability in juev nebula-mesh, published on 23 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47722 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.2
- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.2
- github.com/juev/nebula-mesh (Go): affected all versions; fixed in 0.3.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47722/ (Markdown: https://insights.sbomify.com/CVE-2026-47722/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47722
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47722
- OSV: https://osv.dev/vulnerability/CVE-2026-47722

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47722/
Summaries are generated and may contain mistakes; the official description above is the record.