# CVE-2026-108929: Netcore NR268 DDNS DDNSset.cgi execvp argument injection

> Remote attackers can execute arbitrary commands on Netcore NR268 routers via argument injection in the DDNS Hostname field.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X`)
- **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:** 12 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-q83v-h5qh-mxfc

## What is CVE-2026-108929?

CVE-2026-108929 is a critical command injection vulnerability in Netcore NR268, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw has been found in Netcore NR268 1.7.121109. The affected element is the function execvp of the file /router/DDNSset.cgi of the component DDNS. Executing a manipulation of the argument Hostname can lead to argument injection. The attack can be launched remotely.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-108929 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108929 is a critical command injection vulnerability in Netcore NR268, published on 12 Oct 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-108929 in the wild and no public exploit code.

Affected product: Netcore NR268. 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-108929/ (Markdown: https://insights.sbomify.com/CVE-2026-108929/index.md)
```

## Sources

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

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