# CVE-2026-72603: wg-easy wg-easy - OS Command Injection

> Attackers with client creation permissions can inject commands into WireGuard configs to execute arbitrary code as root.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-g5jq-gh88-3gmw

## What is CVE-2026-72603?

CVE-2026-72603 is a critical command injection vulnerability in wg-easy, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An OS command injection vulnerability in wg-easy 15.3.0 allows users with the clients.create permission to execute arbitrary commands as root by injecting newline-delimited WireGuard PostUp directives into the client name field. The client name is written to the WireGuard configuration file without neutralizing newline characters, allowing injection of arbitrary directives that are executed by wg-quick with root privileges. An attacker with clients.create permission achieves root code execution on the host.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

No fix has been published for CVE-2026-72603 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72603 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72603 is a critical command injection vulnerability in wg-easy, published on 11 Aug 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-72603 in the wild and no public exploit code.

Affected product: wg-easy. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-72603/ (Markdown: https://insights.sbomify.com/CVE-2026-72603/index.md)
```

## Sources

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

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