# CVE-2026-38063: Command injection in n/a

> Attackers can execute arbitrary commands on Tenda 5G03 routers via the ia parameter in the action_radio_on_with_ia_apn function.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-235f-qxww-6764

## What is CVE-2026-38063?

CVE-2026-38063 is a critical command injection vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Tenda 5G03 V05.03.02.04 (Version 1.0) is vulnerable to Command injection in the function action_radio_on_with_ia_apn via the ia parameter.

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

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


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

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

## Is CVE-2026-38063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-38063 is a critical command injection vulnerability in n/a, published on 15 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-38063 in the wild and no public exploit code.

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

## Sources

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

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