Quick answers
- Is CVE-2026-19983 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-19983 being exploited in the wild.
- How severe is CVE-2026-19983?
- High severity, with a CVSS score of 8.3, published 17 August 2026.
- Which products and versions are affected?
- GL.iNet A1300 4.8.x; GL.iNet AX1800 4.8.x; GL.iNet AXT1800 4.8.x; GL.iNet MT2500 4.8.x; and 4 more.
- Is there a fix for CVE-2026-19983?
- A patch was published on 2026: Version 4.9.0 and later address this issue Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-19983 attacked?
- It is attacked over the network, in device firmware.
- Am I affected by CVE-2026-19983?
- Check whether you run GL.iNet A1300, GL.iNet AX1800, GL.iNet AXT1800 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the NAS Command Service (/usr/bin/gl_nas_sys) and involves two chained weaknesses: (1) an authentication bypass in the NAS API token check that can be exploited by sending a Host header of 127.0.0.1, and (2) OS command injection in the GL_NAS_EXEC_FILE API endpoint through shell metacharacters in crafted filenames. The service becomes reachable on port 6000 when an administrator accesses the Network Storage feature in the web portal. No authentication is required; the attack is remotely exploitable from any network-reachable position. Successful exploitation results in unauthenticated remote code execution as root. Firmware version 4.9.0 and later address this issue.
Affected products
- GL.iNet A1300 4.8.x
- GL.iNet AX1800 4.8.x
- GL.iNet AXT1800 4.8.x
- GL.iNet MT2500 4.8.x
- GL.iNet MT3000 4.8.x
- GL.iNet MT6000 4.8.x
- GL.iNet X3000 4.8.x
- GL.iNet XE3000 4.8.x
Timeline
- 2026-08-17: disclosed
- 2026: patched: Version 4.9.0 and later address this issue