# CVE-2026-19983: GL.iNet XE3000 NAS Command Service gl_nas_sys os command injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** GHSA-q36r-pjg6-prm8

## What is CVE-2026-19983?

CVE-2026-19983 is a medium-severity vulnerability in GL.iNet A1300, published on 17 Aug 2026. 

### Official description

A vulnerability was detected in GL.iNet A1300, AX1800, AXT1800, MT2500, MT3000, MT6000, X3000 and XE3000 4.8.x. This issue affects some unknown processing of the file /usr/bin/gl_nas_sys of the component NAS Command Service. The manipulation results in os command injection. The attack may be launched remotely. Upgrading to version 4.9.0 is capable of addressing this issue. It is suggested to upgrade the affected component. The vendor explains: "After our investigation, we have confirmed that the vulnerability described (...) does indeed exist."

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

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


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

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

## Is CVE-2026-19983 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19983 is a medium-severity vulnerability in GL.iNet A1300, published on 17 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-19983 in the wild and no public exploit code.

Affected product: GL.iNet A1300. 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-19983/ (Markdown: https://insights.sbomify.com/CVE-2026-19983/index.md)
```

## Sources

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

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